Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Due to an error in detecting whether resource groups are managed, pcs sometimes could not delete a cloned resource group or a master or slave resource group. With this update, pcs detects the status of resource groups correctly, and deleting the mentioned resource groups proceeds normally.
Description of problem:
If a group of resources is put into a Clone or a Master/Slave set, it cannot be deleted by using the group name. This was possible in older builds, thus the Regression keyword.
Version-Release number of selected component (if applicable):
pcs-0.9.120-2.el6
How reproducible:
Always
Steps to Reproduce:
1. pcs resource create dummy0 Dummy --group group0
2. pcs resource clone group0
3. pcs resource delete group0
Actual results:
[root@virt-021 ~]# pcs resource delete group0
Removing group: group0 (and all resources within group)
Stopping all resources in group: group0...
Error: unable to find a resource/clone/master/group: group0
Expected results:
[root@virt-021 ~]# pcs resource delete group0
Removing group: group0 (and all resources within group)
Stopping all resources in group: group0...
Deleting Resource (and group and clone) - dummy0
Additional info:
Working correctly in pcs-0.9.101-3.el6 and also in pcs-0.9.115-32.el7.
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