I'm trying to recreate a complete cluster setup from blank using puppet. Everything up to this point works, but now the cluster doesn't promote the DRBD resource on either node.
This is the working cluster configuration that I'm trying to recreate:
This is the result of the puppet recipe:
The only differences that I can spot are that
the drbd resource's slave monitor operation is missing
the colocation's resources are switched around
pupped added a default-value "symmetrical=true" in the order resource
According to my understanding the colo should not matter, since it just specifies that both resources MUST run on the same node, but does not mean they must run in any specific order. That's what the order resource is for.
The "symmetrical=true" just means that mysql must be stopped before the other node can be promoted in the ms resource. This should not matter either.
That leaves us with the missing monitor operation. This is the puppet config that leads to this result:
Yes, in this config there is a second monitor op, and it's commented out. If I un-comment it, the slave monitor op with an interval of 61s replaces the master op.
(Sidenote: Corosync/Pacemaker refuses the config if both have the same value for the interval.)
How can I get both monitor ops from puppet into the cluster config?
Is something else wrong with the config that you can spot?