On Wed, May 5, 2010 at 7:56 AM, Smaïne Kahlouch <smain...@free.fr> wrote: > Hi everyone, > > Yesterday i tried several times to migrate resources from a node to > another with the following command : > crm > resource move ldap-grp node2 > > nothing appends.... > when i look to the configuration the "location" rule has been created > but the resource stays in the node1. > I have a test cluster in a test environment (another network) with > exactly the same configuration (corosync/pacemaker) as my production > cluster and the migration works perfectly.
Do you have resource-stickiness == INFINITY? That might cause this. Or perhaps the resource previously failed on the node you're trying to move it to. That could also be a factor. > > 2 differences : > - The production clusters works with two interfaces. This configuration > worked when i previously installed it (last month). > - a new cluster has been created last week in the same network. The > multicast address and port has been changed in corosync.conf. > > I was wondering if there could be a conflicts between the two clusters, > even if multicast address and port has been changed ? > > Regards, > Smaïne > > > _______________________________________________ > 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 > _______________________________________________ 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
