[ClusterLabs] start vs promote drbd m/s colocation constraint

[Brent Jensen]

I've been trying to get my DRBD cluster on Centos8 / Pacemaker 2 to work 
but have had issues with cluster not failing over (I get error messages 
like "Refusing to be Primary while peer is not outdated"). This has been 
explained in other posts. In trying different things I changed my 
constraint from PROMOTE to START and things seem to be working:

DOES NOT WORK (works in pacemaker <2)
pcs constraint order PROMOTE drbd0-clone then start fs_drbd

SEEMS TO WORK
pcs constraint order START drbd0-clone then start fs_drbd

Note: The colocation constraint seems to work even if it's:

  * "pcs constraint colocation add fs_drbd with drbd0-clone INFINITY
    with-rsc-role=Master id=nfs_on_drbd"
  * or just "pcs constraint colocation add fs_drbd with drbd0-clone"

What's the correct way for constraints on M/S DRBD? It just feels wrong 
doing just "start" instead of "promote" like I've been doing over the 
last 15 years. In pacemaker 2.x the master/slave resource changed to 
clone so this is new to me.

Any input is most helpful!

Brent




-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20210202/28ab2108/attachment.htm>