On Wed, Mar 28, 2012 at 4:26 PM, Brian J. Murrell <br...@interlinx.bc.ca> wrote: > We seem to have occasion where we find crm_resource reporting that a > resource is running on more (usually all!) nodes when we query right > after adding it: > > # crm_resource -resource chalkfs-OST0000_3 --locate > resource chalkfs-OST0000_3 is running on: chalk02 > resource chalkfs-OST0000_3 is running on: chalk03 > resource chalkfs-OST0000_3 is running on: chalk04 > resource chalkfs-OST0000_3 is running on: chalk01 > > Further checking reveals: > > # crm status > ============ > Last updated: Mon Dec 19 11:30:31 2011 > Stack: openais > Current DC: chalk01 - partition with quorum > Version: 1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87 > 4 Nodes configured, 4 expected votes > 3 Resources configured. > ============ > > Online: [ chalk01 chalk02 chalk03 chalk04 ] > > MGS_1 (ocf::hydra:Target): Started chalk01 > chalkfs-OST0000_3 (ocf::hydra:Target) Started [ chalk02 chalk03 > chalk04 chalk01 ] > resource chalkfs-OST0000_3 is running on: chalk02 > resource chalkfs-OST0000_3 is running on: chalk03 > resource chalkfs-OST0000_3 is running on: chalk04 > resource chalkfs-OST0000_3 is running on: chalk01 > > Clearly this resource is not running on all nodes, so why is it > being reported as such?
Probably because your resource agent reports OCF_SUCCESS on a probe operation when it ought to be returning OCF_NOT_RUNNING. Pastebin the source of ocf:hydra:Target and someone will be able to point you to the exact part of the RA that's causing the problem. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
