On Fri, Feb 26, 2010 at 10:55 AM, Sebastian Urban <urban...@gmail.com> wrote: > On Mon, 2010-02-22 at 21:12 +0100, Andrew Beekhof wrote: >> On Sat, Feb 13, 2010 at 9:14 PM, Sebastian Urban <urban...@gmail.com> wrote: >> > Hi. >> > >> > I have two servers (cipvm1, cipvm2) and want to configure automatic >> > failover of virtual machines (KVM via libvirt). Both servers share a >> > virtual block device via DRBD in dual primary mode. I use an OCFS2 >> > filesystem for storage of the virtual machines on top of DRBD. Pacemaker >> > is in full control of DRBD, OCFS2 and the virtual machines. Everything >> > seems to run fine. >> > >> > However, let's assume that the VM "ciptest" is started on cipvm2. If >> > cipvm1 (not 2) fails or is put into standby then "ciptest" is stopped >> > and restarted on cipvm2 without any reason. I suspect that Pacemaker >> > thinks that it has to restart the Clone Set vmfs on cipvm2 and therefore >> > also restarts the VM. How can I stop Pacemaker from doing that? >> >> In your version, change the ordering constraint to use a score of 0 >> instead of inf. >> >> I thought I had this figured out for 1.0.7, but I'm told there are >> still some corner cases. >> You might have more luck. > > Okay, so it's a bug. I already work around it by taking control of OCFS2 > away from Pacemaker. I will try again after it's fixed.
Did you try the work-around? _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
