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 1108778 - 'pcs resource unclone group-clone' removes all the group resources but the first one
Summary: 'pcs resource unclone group-clone' removes all the group resources but the fi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: pre-dev-freeze
: 6.6
Assignee: Tomas Jelinek
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-12 14:32 UTC by michal novacek
Modified: 2014-10-14 07:22 UTC (History)
5 users (show)

Fixed In Version: pcs-0.9.123-4.el6
Doc Type: Bug Fix
Doc Text:
Previously, the pcs utility did not properly handle clones of a group when removing resources from the cloned group. As a consequence, the "pcs resource unclone" and "pcs resource delete" commands removed only the first resource in a group when they were supposed to remove the entire resource group. With this update, pcs handles resources in cloned groups correctly and removing cloned resource groups works as expected.
Clone Of:
Environment:
Last Closed: 2014-10-14 07:22:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (11.83 KB, patch)
2014-06-13 14:02 UTC, Tomas Jelinek 		no flags Details | Diff
proposed fix (12.01 KB, patch)
2014-06-16 12:31 UTC, Tomas Jelinek 		no flags Details | Diff
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1526 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2014-10-14 01:22:04 UTC

Description michal novacek 2014-06-12 14:32:07 UTC 
Description of problem:
Uncloning group of resources removes all but the first resource. 

Version-Release number of selected component (if applicable):
pcs-0.9.115-32.el7.x86_64
pacemaker-1.1.10-29.el7.x86_64

How reproducible: always

Steps to Reproduce:
1. for a in 1 2 3; do pcs resource create dummy-$a Dummy --group dummies; done
2. pcs resource clone dummies
3. pcs resource unclone dummies-clone

Actual results: all but first resource in a group removed

Expected results: same effect as running 'pcs resource unclone dummies' which
is only removing the clone.
Comment 3 Tomas Jelinek 2014-06-13 14:02:01 UTC 
Created attachment 908589 [details]
proposed fix
Comment 4 Tomas Jelinek 2014-06-16 12:31:45 UTC 
Created attachment 909116 [details]
proposed fix
Comment 6 Chris Feist 2014-07-03 22:31:03 UTC 
Before Fix:

[root@bid-06 ~]# rpm -q pcs
pcs-0.9.123-3.el6.x86_64
[root@bid-06 ~]# for a in 1 2 3; do pcs resource create dummy-$a Dummy --group dummies; done
[root@bid-06 ~]# pcs resource --full
 Group: dummies
  Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
               stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)
  Resource: dummy-2 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-2-start-timeout-20)
               stop interval=0s timeout=20 (dummy-2-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-2-monitor-interval-10)
  Resource: dummy-3 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-3-start-timeout-20)
               stop interval=0s timeout=20 (dummy-3-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-3-monitor-interval-10)
[root@bid-06 ~]# pcs resource clone dummies
[root@bid-06 ~]# pcs resource --full
 Clone: dummies-clone
  Group: dummies
   Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
                stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)
   Resource: dummy-2 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-2-start-timeout-20)
                stop interval=0s timeout=20 (dummy-2-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-2-monitor-interval-10)
   Resource: dummy-3 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-3-start-timeout-20)
                stop interval=0s timeout=20 (dummy-3-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-3-monitor-interval-10)
[root@bid-06 ~]# pcs resource unclone dummies-clone
[root@bid-06 ~]# pcs resource --full
 Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
  Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
              stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
              monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)


No resources should have been removed and we should have been left with the "dummies group"

After Fix:
[root@bid-06 pcs]# rpm -q pcs
pcs-0.9.123-4.el6.x86_64
[root@bid-06 pcs]# for a in 1 2 3; do pcs resource create dummy-$a Dummy --group dummies; done
[root@bid-06 pcs]# pcs resource --full
 Group: dummies
  Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
               stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)
  Resource: dummy-2 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-2-start-timeout-20)
               stop interval=0s timeout=20 (dummy-2-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-2-monitor-interval-10)
  Resource: dummy-3 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-3-start-timeout-20)
               stop interval=0s timeout=20 (dummy-3-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-3-monitor-interval-10)
[root@bid-06 pcs]# pcs resource clone dummies
[root@bid-06 pcs]# pcs resource --full
 Clone: dummies-clone
  Group: dummies
   Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
                stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)
   Resource: dummy-2 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-2-start-timeout-20)
                stop interval=0s timeout=20 (dummy-2-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-2-monitor-interval-10)
   Resource: dummy-3 (class=ocf provider=heartbeat type=Dummy)
    Operations: start interval=0s timeout=20 (dummy-3-start-timeout-20)
                stop interval=0s timeout=20 (dummy-3-stop-timeout-20)
                monitor interval=10 timeout=20 (dummy-3-monitor-interval-10)
[root@bid-06 pcs]# pcs resource unclone dummies-clone
[root@bid-06 pcs]# pcs resource --full
 Group: dummies
  Resource: dummy-1 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-1-start-timeout-20)
               stop interval=0s timeout=20 (dummy-1-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-1-monitor-interval-10)
  Resource: dummy-2 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-2-start-timeout-20)
               stop interval=0s timeout=20 (dummy-2-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-2-monitor-interval-10)
  Resource: dummy-3 (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-3-start-timeout-20)
               stop interval=0s timeout=20 (dummy-3-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-3-monitor-interval-10)
Comment 9 errata-xmlrpc 2014-10-14 07:22:15 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.

http://rhn.redhat.com/errata/RHBA-2014-1526.html
Note You need to log in before you can comment on or make changes to this bug.