[Pacemaker] 1.1.10 rc7 + final strange behaviour

[Johan Huysmans]

Hi,

I was testing the latest rc7 and the final version of 1.1.10.

My test is the combination of cloned resources and 1 resource group 
containing constraints that the resource group can only run on a node 
where the cloned resource is running

With a 1 node setup everything works ok.
Triggering a failure in the cloned resource triggered a stop of the 
resource group.
Recovering the failure in the cloned resource triggered a recovery of 
the group.

I added my other node, and performed the same failure.
However here strange things happened.
The failure is not correctly shown in crm_mon. A failing resource can be 
shown as ok and and when it is recovered it can be shown a failing.
The resource group is still running on the node of the cluster where the 
cloned resource is failing, however this should failover.

It seems that something got broken in one of the latest rc's as this did 
work.


I included in a crm_report of the moment where a cloned resource failed.

Greetings,
Johan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcmk-Mon-29-Jul-2013.tar.bz2
Type: application/x-bzip
Size: 99761 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130729/1af1afa7/attachment-0003.bin>