Red Hat Bugzilla – Bug 1249085
'pcs resource delete' doesn't delete resource referenced in acl
Last modified: 2016-11-03 16:55:05 EDT
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@redhat.com 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