[Pacemaker] BUG: migrating of colocated resources with m/s resource

[Andrew Beekhof]

On Thu, Jan 21, 2010 at 10:35 PM, Rasto Levrinc
<rasto.levrinc at linbit.com> wrote:
> Hi Beekhof,
>
> I've found a bug, if there is no other explanation for it. It's pacemaker
> 1.0.7 and most likely the versions before.
>
> I have one Stateful Master/Slave resource, that is started before and is
> colocated with Dummy(1) resource, with promoting roles etc. I have another
> resource Dummy(2) that is simply colocated with Dummy(1).
>
> Now when I migrate Dummy(2) resource, it does not migrate to other node

It probably prefers the existing host (due to the colocation with
Dummy1) just as much as the new host.
You'd need to pass --force to crm_resource -- not sure if thats
possible with the shell.

(In this context, --force will set a -INFINITY constraint for the
existing location, forcing the resource to move).

> itself nor Dummy(1) and does not promote/demote anything in Stateful
> resource. When I migrate Dummy(1), everything works as expected.
>
> The targeted test case with migration constraint is attached.
> dc-version disappeared from xml again in unrelated bug, if lmb asks. :) I
> think it happens after cibadmin -E --force.
>
> Thanks,
> Rasto
>
> --
> : Dipl-Ing Rastislav Levrinc
> : DRBD-MC http://www.drbd.org/mc/management-console/
> : DRBD/HA support and consulting http://www.linbit.com/
> DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>