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.
Bug 1187571 - ungrouping a resource from a cloned group produces invalid CIB when other resources exist in that group
Summary: ungrouping a resource from a cloned group produces invalid CIB when other res...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-30 12:30 UTC by Radek Steiger
Modified: 2015-11-19 09:34 UTC (History)
3 users (show)

Fixed In Version: pcs-0.9.140-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: User removes a resource from a cloned group. Consequence: Pcs produces an invalid CIB which is rejected by the cluster, so the resource is not removed from the cloned group. Fix: Detect that the group is cloned and remove the resource from the group properly. Result: Resource is removed from the cloned group properly.
Clone Of:
Environment:
Last Closed: 2015-11-19 09:34:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (3.88 KB, patch)
2015-02-20 13:18 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1156311 0 high CLOSED Need ability to start resource and wait until it finishes starting before returning (and show error information if it fa... 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1188571 0 high CLOSED The --wait functionality implementation needs an overhaul 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2015:2290 0 normal SHIPPED_LIVE Moderate: pcs security, bug fix, and enhancement update 2015-11-19 09:43:53 UTC

Internal Links: 1156311 1188571

Description Radek Steiger 2015-01-30 12:30:14 UTC 
> Description of problem:

It is not possible to remove a resource from a group using 'pcs resource unclone' when the group is cloned and at the same time other resources exist in this group.


> Version-Release number of selected component (if applicable):

pcs-0.9.137-13.el7


> How reproducible:

Always


> Steps to Reproduce:

1. pcs resource create dummyX Dummy --group groupX
2. pcs resource create dummyY Dummy --group groupX
3. pcs resource clone groupX
4. pcs resource ungroup groupX dummyY


> Actual results:

# pcs resource ungroup groupX dummyY
Error: Unable to update cib
Call cib_replace failed (-203): Update does not conform to the configured schema
...

The CIB snippet looks like this - the dummyY resource is moved out of the groupX, but only to be left inside the clone, which is not valid:

<clone id="groupX-clone">
  <group id="groupX">
    <primitive class="ocf" id="dummyX" provider="heartbeat" type="Dummy">
      <instance_attributes id="dummyX-instance_attributes"/>
      <operations/>
    </primitive>
  </group>
  <meta_attributes id="groupX-clone-meta"/>
  <primitive class="ocf" id="dummyY" provider="heartbeat" type="Dummy">
    <instance_attributes id="dummyY-instance_attributes"/>
    <operations/>
  </primitive>
</clone>
Comment 1 Tomas Jelinek 2015-02-20 13:18:54 UTC 
Created attachment 993907 [details]
proposed fix
Comment 3 Tomas Jelinek 2015-06-04 14:43:19 UTC 
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el6.x86_64
[root@rh71-node1:~]# pcs resource create d1 dummy --group dummies
[root@rh71-node1:~]# pcs resource create d2 dummy --group dummies
[root@rh71-node1:~]# pcs resource clone dummies
[root@rh71-node1:~]# pcs resource
 Clone Set: dummies-clone [dummies]
     Started: [ rh71-node1 rh71-node2 rh71-node3 ]
[root@rh71-node1:~]# pcs resource ungroup dummies d2
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 d1 dummy --group dummies
[root@rh71-node1:~]# pcs resource create d2 dummy --group dummies
[root@rh71-node1:~]# pcs resource clone dummies
[root@rh71-node1:~]# pcs resource
 Clone Set: dummies-clone [dummies]
     Started: [ rh71-node1 rh71-node2 rh71-node3 ]
[root@rh71-node1:~]# pcs resource ungroup dummies d2
[root@rh71-node1:~]# pcs resource
 Clone Set: dummies-clone [dummies]
     Started: [ rh71-node1 rh71-node2 rh71-node3 ]
 d2     (ocf::heartbeat:Dummy): Started rh71-node3
Comment 7 errata-xmlrpc 2015-11-19 09:34:32 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.