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.
> Description of problem:
When using pcs 0.9.143 to manage an older cluster with pcs older than 0.9.143, deleting groups and/or clones in the tree view returns an Internal Server Error.
The problem is in the list of resources to be removed which includes both the group/clone name AND all the primitives inside. The old backend then tries to delete the group/clone first and then the primitives second, which are already gone however with the group/clone removal:
I, [2015-11-30T13:32:18.872390 #10163] INFO -- : Running: /usr/sbin/pcs --force resource delete group21
I, [2015-11-30T13:32:19.868892 #10163] INFO -- : Running: /usr/sbin/pcs --force resource delete dummy21
I, [2015-11-30T13:32:20.136211 #10163] INFO -- : Remove resource errors:
Unable to remove: dummy21
::ffff:10.15.105.137 - - [30/Nov/2015 13:32:20] "POST /remote/remove_resource HTTP/1.1" 500 26 1.3123
::ffff:10.15.105.137 - - [30/Nov/2015 13:32:20] "POST /remote/remove_resource HTTP/1.1" 500 26 1.3125
::ffff:10.15.105.137 - - [30/Nov/2015:13:32:18 CET] "POST /remote/remove_resource HTTP/1.1" 500 26
- -> /remote/remove_resource
This should be fixed on the GUI side because only the parent should be sent in the list if the whole group/clone is meant to be removed. Also, please don't forget about the Select All tickbox is causing the same issue.
> Version-Release number of selected component (if applicable):
pcs-0.9.143-15.el7 (RHEL7.2)
+
pcs-0.9.137-13.el7_1.5 (RHEL7.1)
> How reproducible:
Always
> Steps to Reproduce:
1. Add a RHEL7.1 based cluster into RHEL7.2 GUI
2. Add a resource group/clone
3. Remove the whole group/clone by selecting the group/clone tickbox
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-2016-2596.html