<div dir="ltr">Hello all,<div><br></div><div>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.</div><div><br></div>
<div>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.</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>Here are my options:</div><div><div>property $id="cib-bootstrap-options" \</div>
<div> dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \</div><div> cluster-infrastructure="openais" \</div><div> expected-quorum-votes="3" \</div><div> stonith-enabled="false" \</div>
<div> last-lrm-refresh="1385395648" \</div><div> no-quorum-policy="freeze"</div><div><br></div><div>rsc_defaults $id="rsc-options" \</div><div> resource-stickiness="1000"</div>
</div><div><br></div><div>Do you know if there is a bug with this 1.1.6 version or am I missing something?</div><div><br></div><div>Logs are available at <a href="http://pastebin.com/Jxgq3MRH">http://pastebin.com/Jxgq3MRH</a></div>
<div>I know there is an issue with the cinder-HDD1 resources. It is not yet correctly configured</div></div>