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 you create a resource and an acl rule that reference the id of resource, 'pcs resource delete' doesn't remove the resource even when you specify --force option.


Version-Release number of selected component (if applicable):
pcs-0.9.142-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. # pcs resource create dummy Dummy
2. # pcs acl role create read-dummy read id dummy
3. # pcs resource delete dummy
4. # pcs resource delete dummy --force


Actual results:
# pcs resource delete dummy
Attempting to stop: dummy...Stopped
Error: unable to remove resource: dummy, it may still be referenced in constraints.
# pcs resource delete dummy --force
Deleting Resource - dummy
Error: unable to remove resource: dummy, it may still be referenced in constraints.
# pcs resource
 dummy  (ocf::heartbeat:Dummy): (target-role:Stopped) Stopped

Expected results:
pcs deletes the resource or correctly inform that the resource is referenced in an acl.

Bumping to 7.3 as we are late in 7.2.

Created attachment 1121401 [details]
proposed fix

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Before fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.143-15.el7.x86_64

[vm-rhel72-1 ~] $ pcs resource create dummy Dummy
[vm-rhel72-1 ~] $ pcs acl role create read-dummy read id dummy
[vm-rhel72-1 ~] $ pcs resource delete dummy
Deleting Resource - dummy
Error: unable to remove resource: dummy, it may still be referenced in constraints.

After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.151-1.el7.x86_64

[vm-rhel72-1 ~] $ pcs resource create dummy Dummy
[vm-rhel72-1 ~] $ pcs acl role create read-dummy read id dummy
[vm-rhel72-1 ~] $ pcs resource delete dummy
Deleting Resource - dummy

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