[ClusterLabs] When resource fails to start it stops an apparently unrelated resource

[Ken Gaillot]

On Mon, 2017-10-16 at 18:30 +0200, Gerard Garcia wrote:
> Hi,
> 
> I have a cluster with two ocf:heartbeat:anything resources each one
> running as a clone in all nodes of the cluster. For some reason when
> one of them fails to start the other one stops. There is not any
> constrain configured or any kind of relation between them. 
> 
> Is it possible that there is some kind of implicit relation that I'm
> not aware of (for example because they are the same type?)
> 
> Thanks,
> 
> Gerard

There is no implicit relation on the Pacemaker side. However if the
agent returns "failed" for both resources when either one fails, you
could see something like that. I'd look at the logs on the DC and see
why it decided to restart the second resource.
-- 
Ken Gaillot <kgaillot at redhat.com>