Red Hat Bugzilla – Bug 1187320
Uncloning a non-cloned resource produces invalid CIB
Last modified: 2015-11-19 04:34:29 EST
> Description of problem: When trying to unclone a resource, which is not a clone, pcs produces invalid CIB by stripping the resources' parent tag (<resources> in this case). > Version-Release number of selected component (if applicable): pcs-0.9.137-13.el7 > How reproducible: Always > Steps to Reproduce: 1. pcs resource create dummy0 Dummy 2. pcs resource unclone dummy0 > Actual results: The whole <resources> element is stripped from CIB: [root@virt-010 ~]# pcs resource unclone dummy0 Error: Unable to update cib Call cib_replace failed (-203): Update does not conform to the configured schema <cib crm_feature_set="3.0.9" validate-with="pacemaker-2.3" epoch="352" num_updates="0" admin_epoch="0" cib-last-written="Thu Jan 29 19:45:28 2015" have-quorum="1" dc-uuid="2"> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <...snip...> </cluster_property_set> </crm_config> <nodes> <node id="1" uname="virt-010"/> <node id="2" uname="virt-011"/> <node id="3" uname="virt-012"/> <node id="4" uname="virt-016"/> </nodes> <constraints/> <primitive class="ocf" id="dummy0" provider="heartbeat" type="Dummy"> <instance_attributes id="dummy0-instance_attributes"/> <operations> <op id="dummy0-start-timeout-20" interval="0s" name="start" timeout="20"/> <op id="dummy0-stop-timeout-20" interval="0s" name="stop" timeout="20"/> <op id="dummy0-monitor-interval-10" interval="10" name="monitor" timeout="20"/> </operations> </primitive> </configuration>
Created attachment 1005449 [details] proposed fix
Before Fix: [root@rh71-node1 ~]# rpm -q pcs pcs-0.9.137-13.el7_1.2.x86_64 [root@rh71-node1:~]# pcs resource create dummy dummy [root@rh71-node1:~]# pcs resource unclone dummy Error: Unable to update cib Call cib_replace failed (-203): Update does not conform to the configured schema ... After Fix: [root@rh71-node1:~]# rpm -q pcs pcs-0.9.140-1.el6.x86_64 [root@rh71-node1:~]# pcs resource create dummy dummy [root@rh71-node1:~]# pcs resource unclone dummy Error: 'dummy' is not a clone resource [root@rh71-node1:~]# echo $? 1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2290.html