Hello all, I have an issue with the no quorum policy freeze (stonith disabled). I'm using an old version of pacemaker (1.1.6), the one distributed by Ubuntu 12.04.
I have a cluster with 3 nodes running various resources, including drbd. This night, my hosting provider did a maintenance on its network, and all the machines were disconnected. What happened is that every machine promoted the DRBD resources and started the resources on top of them. Using no-quorum-policy="freeze", I was not expecting that. The network came back 1 or 2 minutes later but the damage was already done. All my drbd resources were in a split brain situation. Here are my options: property $id="cib-bootstrap-options" \ dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \ cluster-infrastructure="openais" \ expected-quorum-votes="3" \ stonith-enabled="false" \ last-lrm-refresh="1385395648" \ no-quorum-policy="freeze" rsc_defaults $id="rsc-options" \ resource-stickiness="1000" Do you know if there is a bug with this 1.1.6 version or am I missing something? Logs are available at http://pastebin.com/Jxgq3MRH I know there is an issue with the cinder-HDD1 resources. It is not yet correctly configured
_______________________________________________ Pacemaker mailing list: Pacemaker@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