[Pacemaker] DRBD resources show as running when they don't exist

[Andrew Beekhof]

On 15/09/2013, at 3:14 AM, Stephen Marsh <stephen at serverforce.net> wrote:

> Hi all,
> 
> I'm using Corosync 2.3.1 with Pacemaker 1.1.10 (final release) and DRBD 8.4.3.
> 
> I've got a strange problem with the way Pacemaker handles DRBD resources that don't exist.
> 
> I'm testing with this config:
> 
> primitive vs1-1-DRBD ocf:linbit:drbd \
>        params drbd_resource="vs1-1" \
>        operations $id="vs1-1-DRBD-ops" \
>        op start interval="0" timeout="60s" on-fail="block" \
>        op stop interval="0" timeout="60s" on-fail="block" \
>        op monitor interval="20" role="Master" timeout="50" \
>        op monitor interval="30" role="Slave" timeout="50"
> 
> ms vs1-1-MS vs1-1-DRBD \
>        meta resource-stickiness="100" master-max="2" notify="true" interleave="true" target-role="Started" is-managed="true"
> 
> DRBD resource vs1-1 does not exist at all, and "crm_mon -1" correctly shows that it has failed... but when I run "crm resource show vs1-1-MS" (or "crm resource show vs1-1-DRBD"), it reports that it's running on all members of the cluster.

If crm_mon is reporting it as failed, that suggests there is a problem in crmsh rather than pacemaker.

> 
> If, on the other hand, I create a DRBD config file for vs1-1 but specify a non-existent backing device so that it still can't start, but for a different reason, Pacemaker behaves as expected: it registers the resource as failed and doesn't show the resource as running at all.
> 
> Any help would be most appreciated.
> 
> Thanks
> 
> Regards,
> Stephen Marsh
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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

-------------- 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/20130917/5c0d7d5f/attachment-0004.sig>