[Pacemaker] crm_resource -L not trustable right after restart

Andrew Beekhof andrew at beekhof.net
Tue Jan 14 00:01:25 EST 2014

On 14 Jan 2014, at 3:41 pm, Brian J. Murrell (brian) <brian at interlinx.bc.ca> wrote:

> On Tue, 2014-01-14 at 08:09 +1100, Andrew Beekhof wrote:
>> The local cib hasn't caught up yet by the looks of it.
> Should crm_resource actually be [mis-]reporting as if it were
> knowledgeable when it's not though?  IOW is this expected behaviour or
> should it be considered a bug?  Should I open a ticket?

It doesn't know that it doesn't know.
Does it show anything as running?  Any nodes as online?

I'd not expect that it stays in that situation for more than a second or two...

>> You could compare 'cibadmin -Ql' with 'cibadmin -Q'
> Is there no other way to force crm_resource to be truthful/accurate or
> silent if it cannot be truthful/accurate?  Having to run this kind of
> pre-check before every crm_resource --locate seems like it's going to
> drive overhead up quite a bit.


> Maybe I am using the wrong tool for the job.  Is there a better tool
> than crm_resource to ascertain, with full truthfullness (or silence if
> truthfullness is not possible), where resources are running?

We could add an option to force crm_resource to use the master instance instead of the local one I guess.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140114/6874765b/attachment-0003.sig>

More information about the Pacemaker mailing list