[ClusterLabs] Resource cannot run anywhere

Andrei Borzenkov arvidjaar at gmail.com
Tue Jul 21 07:02:27 UTC 2015


On Mon, Jul 20, 2015 at 4:40 PM, Leonhardt,Christian
<christian.leonhardt at dako.de> wrote:
> Hello everyone,
>
> I already posted this issue at the Debian HA maintainers list (http://l
> ists.alioth.debian.org/pipermail/debian-ha-maintainers/2015
> -July/004325.html). Unfortunately the problem still exist and the
> Debian maintainers told me to ask this list for further assistance. So
> here I am. ;-)
> At the moment i am evaluating a new cluster stack to replace our old
> heartbeat cluster (currently running on Debian Wheezy).  I used the
> guide from https://wiki.debian.org/Debian-HA/ClustersFromScratch.
> At the moment the cluster is running pretty well so far but i stuck at
> the failover tests.
> 'crm node standby' works flawlessly but moving a resource to an other
> node with 'resource move p_lighttpd' for example fails with 'Resource
> cannot run anywhere'. The resource just get stopped. The problem occurs
> when moving the resources p_squid3, p_apache2, p_bind9 or p_lighttpd.
> All other resouces like ip addresses or symlinks are working.
>
> Do i miss something or is it a bug?
>
...
> colocation co_p_lighttpd_with_p_bind9 inf: p_lighttpd p_bind9
...
> native_color: p_bind9 allocation score on s1r3drslfw1: -INFINITY
> native_color: p_bind9 allocation score on s3r2drslfw1: 300
> native_color: p_squid3 allocation score on s1r3drslfw1: -INFINITY
> native_color: p_squid3 allocation score on s3r2drslfw1: 100
> native_color: p_apache2 allocation score on s1r3drslfw1: -INFINITY
> native_color: p_apache2 allocation score on s3r2drslfw1: 100
> native_color: p_lighttpd allocation score on s1r3drslfw1: -INFINITY
> native_color: p_lighttpd allocation score on s3r2drslfw1: -INFINITY
>

You have mandatory colocation constraint for p_lighthttpd to be on the
same node as p_bind9. This is one-way relationship. p_bind9 runs on
s3r2drslfw1 so p_lighttpd can only be ever started on s3r2drslfw1. If
you now set additional location constraint that prohibits it to run on
s3r2drslfw1 it cannot be started anywhere (unless you also move
p_bind9).




More information about the Users mailing list