----- Original Message ----- > From: "James Guthrie" <j...@open.ch> > To: "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org> > Sent: Tuesday, February 5, 2013 8:12:57 AM > Subject: Re: [Pacemaker] Pacemaker resource migration behaviour > > Hi all, > > as a follow-up to this, I realised that I needed to slightly change > the way the resource constraints are put together, but I'm still > seeing the same behaviour. > > Below are an excerpt from the logs on the host and the revised xml > configuration. In this case, I caused two failures on the host mu, > which forced the resources onto nu then I forced two failures on nu. > What can be seen in the logs are the two detected failures on nu > (the "warning: update_failcount:" lines). After the two failures on > nu, the VIP is migrated back to mu, but none of the "support" > resources are promoted with it.
I can't tell much from this output. Run the steps you use to reproduce this and create a crm_report of the issue so we can see both the logs and pengine transition files that proceed this. -- Vossel > Regards, > James > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org