Hi, it seems that once a resource has been configured in pacemaker, even after having deleted it , there is somewhere a ghost of the resource :
For a resource never configured : crm resource status resource-toto Resource resource-toto not found: The object/attribute does not exist Now, let's do it with a resource configured then deleted : crm resource status resource-alain resource resource-alain is running on: node3 crm resource stop resource-alain1 crm resource status resource-alain1 resource resource-alain1 is NOT running crm configure *delete* resource-alain1 INFO: hanging location:loc1-resource-alain1 deleted INFO: hanging location:forbiddenloc-resource-alain1 deleted crm resource status resource-alain1 resource resource-alain1 is NOT running whereas : grep resource-alain1 /var/lib/heartbeat/crm/cib.xml There is no more trace of resource-alain1 in cib.xml, but the crm resource status does not return "The object/attribute does not exist" but returns "is NOT running". Why it is not the same message as if the resource has never been configured ? And where is the "ghost" trace of this deleted resource as there is no trace of it in cib.xml ? PS : this test has been done with pacemaker-1.0.8-6.1.el5 as well as with pacemaker-1.1.2-2.el6 Thanks Regards Alain _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
