RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

> 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