[Linux-cluster] pacemaker location constraint

C. Handel christoph at macht-blau.org
Mon May 26 13:47:32 UTC 2014

>>>> location constraints are somehow not honored by pacemaker 1.1.10 on el6.
>>>> I have an IP adress which is placed first and then a volumegroup and a
>>>> filesystem which choose the same node. The IP should be placed on x432, but
>>>> for some reason it chooses x430. There are additional resources running
>>>> (also choosing strange nodes).
>>>> [...]
>>>> The stripped config is:
>>>> [...]

>>> yeah, don't do that.  we need the whole thing (the cibadmin -Ql output in your case since you're using crmsh)

>> [config]

>  The IP prefers not to run on 432 because vg_service_c is collocated with it and vg_service_c cannot run there:
>    vg_service_c: migration-threshold=1000000 fail-count=1000000 last-failure='Wed May 21 18:52:24 2014'
> (as seen with crm_mon -f)

Thanks a lot. Everything now works as intendend.


More information about the Linux-cluster mailing list