Trusty's "crm configure load" fails to update cluster configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
crmsh (Ubuntu) |
Fix Released
|
Undecided
|
Rafael David Tinoco | ||
Trusty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
* crm configure load update does not work in Trusty.
* it is not possible to restore previous cluster configuration.
[Test Case]
* crm configure save
* crm configure load
* see the error
[Regression Potential]
* based on upstream commit.
* tested by community and assigner. fixes the issue.
* not working today so no potential regression.
[Other Info]
* Original bug description:
----------------
It was brought to me (~inaddy) the following situation:
""""""
* Environment
Ubuntu 14.04 LTS
Pacemaker 1.1.10+
* Issue
I cannot use "crm configure load update".
It cause an error as below.
# crm configure load update settings.crm
ERROR: elements cib-bootstrap-
My pacemaker settings.
-------
property no-quorum-
stonith-
startup-
crmd-transition
rsc_defaults resource-
migration-
group grpStonith1 \
prmStonith1-2
group grpStonith2 \
prmStonith2-2
fencing_topology \
A1MB101: prmStonith1-2 \
A1MB102: prmStonith2-2
primitive prmStonith1-2 stonith:
params \
pcmk_reboot_
hostlist="A1MB101" \
op start interval="0s" timeout="60s" on-fail="restart" \
op monitor interval="10s" timeout="60s" on-fail="restart" \
op stop interval="0s" timeout="60s" on-fail="ignore"
primitive prmStonith2-2 stonith:
params \
pcmk_reboot_
hostlist="A1MB102" \
op start interval="0s" timeout="60s" on-fail="restart" \
op monitor interval="10s" timeout="60s" on-fail="restart" \
op stop interval="0s" timeout="60s" on-fail="ignore"
location rsc_location-
rule -INFINITY: #uname eq A1MB101
location rsc_location-
rule -INFINITY: #uname eq A1MB102
-------
* Request
1. It may be a bug. Can you fix it?
I found this thread.
http://
""""""
I was able to reproduce the following error:
root@trustyclus
ERROR: elements 739246090,
Exporting and trying to re-import my personal cluster configuration.
And based on the public discussion (when this was reported):
http://
I could see developer "fixed" this behavior on Aug 8 2013. After digging a little on crm configure load
I could find that this error came from a file on the package crmsh and on crmsh upstream tree I found this:
<email address hidden>
* Thu Aug 8 09:55:23 2013 Dejan Muhamedagic | b146349 ||| Medium: cibconf: repair configure load update
So I'm assuming (and testing right now) this will fix the issue... Opening the public bug for the fix I'll provide after tests.
Related branches
description: | updated |
Changed in crmsh (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Rafael David Tinoco (inaddy) |
description: | updated |
tags: |
added: verification-node removed: verification-needed |
tags: |
added: verification-done removed: verification-node |
## After applying the fix I could successfully load my previous cluster configuration:
root@trustyclus ter01:~ # crm configure load xml replace ./cluster.xml
root@trustyclus ter01:~ # crm resource external/ vcenter) : Stopped external/ vcenter) : Stopped external/ vcenter) : Stopped external/ vcenter) : Stopped :IPaddr2) : Started
crm(live)resource# list
p_fence_cluster01 (stonith:
p_fence_cluster02 (stonith:
p_fence_cluster03 (stonith:
p_fence_cluster04 (stonith:
clusterip (ocf::heartbeat
crm(live)resource# start all
ERROR: 2: resource all does not exist
crm(live)resource# start p_fence_cluster01
crm(live)resource# start p_fence_cluster02
crm(live)resource# start p_fence_cluster03
crm(live)resource# start p_fence_cluster04
crm(live)resource# end
crm(live)# end
crm(live)# quit
bye
## and resources were active again:
root@trustyclus ter01:~ # crm_mon -1
Last updated: Tue Aug 5 14:22:38 2014
Last change: Tue Aug 5 14:22:20 2014 via cibadmin on trustycluster02
Stack: corosync
Current DC: trustycluster02 (739246088) - partition with quorum
Version: 1.1.10-42f2063
4 Nodes configured
5 Resources configured
Online: [ trustycluster01 trustycluster02 trustycluster03 trustycluster04 ]
p_fence_cluster01 (stonith: external/ vcenter) : Started trustycluster02 external/ vcenter) : Started trustycluster01 external/ vcenter) : Started trustycluster04 external/ vcenter) : Started trustycluster03 :IPaddr2) : Started trustycluster01
p_fence_cluster02 (stonith:
p_fence_cluster03 (stonith:
p_fence_cluster04 (stonith:
clusterip (ocf::heartbeat