[Pacemaker] resource with colocation rule doesn't fail

[Andrew Beekhof]

On 02/08/2013, at 11:33 AM, Andrew Beekhof <andrew at beekhof.net> wrote:

> 
> On 01/08/2013, at 5:38 PM, Johan Huysmans <johan.huysmans at inuits.be> wrote:
> 
>> I forgot to mention:
>> 
>> I'm using a build from git (Version: 1.1.11-1.el6-42f2063).
>> I used the same config on an old 1.1.10 rc (rc6 or before) and that worked, as of rc7 it didn't work anymore.
> 
> I will have a look, but why are you setting on-fail=block for everything?

Ironically the log message for the commit which broke this was:

commit faa883cf7927d84f61f29211fe6e2980de645620
    Bug: cl#5170 - Correctly support on-fail=block for clones


> 
>> 
>> On 01-08-13 09:35, Johan Huysmans wrote:
>>> Hi,
>>> 
>>> I have a cloned resource and a resource group. They have a colocation rule configured in such way that the resource group must be running where the cloned resource is running.
>>> 
>>> When I stop the service in the cloned resource on 1 node, this appears in crm_mon, however the resource group does not get moved to the other node.
>>> 
>>> When I start the service in the cloned resource on that specific node, this gets updated in crm_mon, however this still appears in the logs as stopped.
>>> 
>>> I attached the crm_report for this problem.
>>> 
>>> Thx!
>>> 
>>> gr.
>>> Johan
>> 
>> 
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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
>