[ClusterLabs] Pacemaker responsible of DRBD and a systemd resource

[Derek Wuelfrath]

Hello there,

First post here but following since a while!

Here’s my issue,
we are putting in place and running this type of cluster since a while and never really encountered this kind of problem.

I recently set up a Corosync / Pacemaker / PCS cluster to manage DRBD along with different other resources. Part of theses resources are some systemd resources… this is the part where things are “breaking”.

Having a two servers cluster running only DRBD or DRBD with an OCF ipaddr2 resource (Cluser IP in instance) works just fine. I can easily move from one node to the other without any issue.
As soon as I add a systemd resource to the resource group, things are breaking. Moving from one node to the other using standby mode works just fine but as soon as Corosync / Pacemaker restart involves polling of a systemd resource, it seems like it is trying to start the whole resource group and therefore, create a split-brain of the DRBD resource.

It is the best explanation / description of the situation that I can give. If it need any clarification, examples, … I am more than open to share them.

Any guidance would be appreciated :)

Here’s the output of a ‘pcs config’

https://pastebin.com/1TUvZ4X9 <https://pastebin.com/1TUvZ4X9>

Cheers!
-dw

--
Derek Wuelfrath
dwuelfrath at inverse.ca <mailto:dwuelfrath at inverse.ca> :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110)
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <https://www.sogo.nu/>), PacketFence (www.packetfence.org <https://www.packetfence.org/>) and Fingerbank (www.fingerbank.org <https://www.fingerbank.org/>)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20171109/9be1798b/attachment-0001.html>