On 05/01/2013 10:49 PM, David Vossel wrote:
Have you tested this with 1.1? There have been changes to how migration works,
some of which have to do with properly handling partial migrations. I'd test this
in 1.1.10.rc1 or anything >= 1.1.8
No, we did not try with 1.1 yet.
The patches you
Dear All,
we currently investigate a problem where some Libvirt/KVM VM in a
pacemaker cluster ends up running on two nodes after being migrated.
The problem is triggered when a constraint is inserted that causes the
VM to be migrated away from its current node, but then the constraint is
rem
Hi,
it seems to me that patch
http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/8241f689bf9f
broke timeouts for stop operations. The observable effect is that the
timeout for stop operations is always 125s, regardless what was
specified in the CIB. Reverting the part of the patch that cha
On 29.09.2010 19:59, Mike A Meyer wrote:
We have two nodes that we have the IP address assigned to a bond0
network interface instead of the usual eth0 network interface. We are
wondering if there are issues with trying to configure
corosync/pacemaker with an IP assigned to a bond0 network inte
Hi,
The appended patch is for the bug described in
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2456 found in
pacemaker 1.0.9.1,
Apparently "crm_resource" calls "unpack_constraints()" for some actions
( -A, -a) but later does not free the memory allocated during that call.
Usin
