Red Hat Bugzilla – Bug 1199073
creating a resource name colliding with an existing group/clone/master ID needs better error message
Last modified: 2015-11-19 04:36:06 EST
> Description of problem: If a grouped/cloned/MS resource already exists in a cluster and a new resource, which name is identical to an ID of that group/clone/MS, an invalid CIB is produced instead of a proper error message. We could get an inspiration from adding a colliding resource ID, where we have a proper error message: "Error: unable to create resource/fence device 'dummy0', 'dummy0' already exists on this system" > Version-Release number of selected component (if applicable): pcs-0.9.137-10.el7 > How reproducible: Always > Steps to Reproduce: 1. pcs resource create dummy0 Dummy --clone 2. pcs resource create dummy0-clone Dummy > Actual results: Error: Unable to update cib Call cib_replace failed (-203): Update does not conform to the configured schema ... > Expected results: "Error: unable to create resource/fence device 'dummy0-clone', 'dummy0-clone' already exists on this system"
Created attachment 1011674 [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 --clone [root@rh71-node1:~]# pcs resource Clone Set: dummy-clone [dummy] Started: [ rh71-node1 rh71-node2 rh71-node3 ] [root@rh71-node1:~]# pcs resource create dummy-clone 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 --clone [root@rh71-node1:~]# pcs resource Clone Set: dummy-clone [dummy] Started: [ rh71-node1 rh71-node2 rh71-node3 ] [root@rh71-node1:~]# pcs resource create dummy-clone dummy Error: unable to create resource/fence device 'dummy-clone', 'dummy-clone' already exists on this system [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