Hi all,
I’ve a pacemaker cluster controlling drbd volumes in an active-passive-setup. Following the documentation the fence handler crm-fence-peer.9.sh is configured.
As far as I understand does the fence handler inject location constraints into the cib based on the status of the drbd devices. Now to the problem which seems to be true including the current version 9.33.0 of drbd-utils. Since pacemaker 2.1 the roles of a cloned resource are named Promoted/Unpromoted in contrast to the older Master/Slave. But crm-fence-peer.9.sh is injecting a location constraint with a deprecated role Master. Currently this is “only” a warning I get, but I want to avoid a future breakage. So I would be happy to see a solution with correct role names depending on the pacemaker version in use.
Please don’t hesitate to ask for further information.
Best regards
Andreas