<tt><font size=2>>> I have the following scenario that I am trying
to simulate.<br>>> <br>>> I have a volume replicated between clusters A and B, primary on
cluster A.<br>>> The volume is attached to and mounted on a VM instance VM1 on
cluster A.<br>>> I take a snapshot of VM1.<br>>> I now imagine that VM1 on cluster A becomes unreachable, so I
want to <br>>> bring up VM1 on cluster B, and attach to it the replicated volume.<br>>> I have to make the volume primary on cluster B.<br>>> As long as the volume is primary on cluster A, I cannot make it
primary on <br>>> cluster B.<br>>> <br>>> I want to force the transition of the volume on cluster B from
secondary <br>>> to primary, without having to perform operations on cluster A.<br>>> <br>>> What is the proper sequence of operations / commands to accomplish
this?<br>>As in your expected experiment, you will need to cut the communication
path <br>>between the two sites.<br><br>>The easiest way to do so is to run "drbdadm disconnect <resource>"
on one <br>>of the sites; given your requirements, on cluster B.<br></font></tt><br><tt><font size=2>This changes the state of the volume on cluster B
to "OutDated" and I am unable</font></tt><br><tt><font size=2>to change the volume to primary. I seem to still be
missing something.</font></tt><br><br><tt><font size=2>I tried to do --force to make the volume primary,
but then I was unable to</font></tt><br><tt><font size=2>import it to (OpenStack) cinder and attach it to an
instance, since the id was</font></tt><br><tt><font size=2>not recognized.</font></tt><br><br><tt><font size=2>- Kalman<br></font></tt><br><BR>