Red Hat Bugzilla – Bug 902459
Persistent resource-related data after the resource is deleted
Last modified: 2013-11-21 07:08:44 EST
Description of problem: Pacemaker still keeps data about resources (or better, their related ops) that have already been deleted. This negatively influences any new resource created with the same name. One has to do "crm_resource --resource dummystateful --cleanup" Version-Release number of selected component (if applicable): pacemaker-1.1.8-7.el6.x86_64 How reproducible: always Steps to Reproduce: 1. pcs resource create dummystateful nonsense op monitor interval="5s" (invalid resource agent is intended) 2. pcs resource delete dummystateful 3. pcs resource create dummystateful ocf:pacemaker:Stateful 4. (optional) crm_resource --resource dummystateful --cleanup Actual results: after step 1 (and before step 2) following info is printed: pengine[32644]: notice: unpack_rsc_op: Preventing dummystateful from re-starting on marathon-03c2-node03: operation monitor failed 'not installed' (rc=5) That is expected. But the same is printed from fresh resource in step 3. Step 4 resolves the situation. Expected results: all resource related data and data about operations related to the resource should be deleted together with the resource so no newly created resource is influenced. Additional info:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Traditionally this was for the admin to clean up, however David and I agree with your expectations. He has a patch almost ready to go upstream.
I patch has been committed for this upstream https://github.com/ClusterLabs/pacemaker/commit/57a53082c5123500a15c99a2f1ff702230f2fdd0
Current expectation is that we'll pick this up in a rebase for 6.5
No leftover found after running reproducer in comment 0. cibadmin -Q | grep dummy shows nothing either. pacemaker-1.1.10-9.el6.x86_64 pcs-0.9.82-1.el6.noarch Marking as verified.
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/RHSA-2013-1635.html