<font size=2 face="sans-serif">I am running the following on three RHEL
7.2 Server VMs:</font>
<br><font size=2 face="sans-serif">drbd-bash-completion-8.9.6-1</font>
<br><font size=2 face="sans-serif">drbdmanage-0.96.1-1</font>
<br><font size=2 face="sans-serif">drbd-udev-8.9.6-1</font>
<br><font size=2 face="sans-serif">drbd-utils-8.9.6-1</font>
<br><font size=2 face="sans-serif">kmod-drbd-9.0.1_3.10.0_327.18.2-1</font>
<br>
<br><font size=2 face="sans-serif">When I added the second and third nodes
to the cluster I got a number of messages like:</font>
<br><font size=2 face="sans-serif">drbd .drbdctrl: State change failed:
Peer may not become primary while device is opened read-only</font>
<br>
<br><font size=2 face="sans-serif">Running dmesg on the node from which
I issued all the drbdmanage commands I see some messages like:</font>
<br><font size=2 face="sans-serif">Failed: peer( Secondary -> Primary
)</font>
<br><font size=2 face="sans-serif">Aborting remote state change x</font>
<br>
<br><font size=2 face="sans-serif">I also see a couple of messages like:</font>
<br><font size=2 face="sans-serif">Rejecting concurrent remote state change
y because of state change z</font>
<br>
<br><font size=2 face="sans-serif">Running "drbdmanage list-nodes"
shows all the nodes as ok so is it safe to ignore these messages?<br>
<br>
Regards, John Colgrave<br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>