[ClusterLabs] cloned resources ordering and remote nodes problem

[Radoslaw Garbacz]

Thank you, however in my case this parameter does not change the described
behavior.

I have a more detail example:
order: res_A-clone -> res_B-clone -> res_C
when "res_C" is not on the node, which had "res_A" instance failed, it will
not be restarted, only "res_A" and "res_B" all instances will.

I implemented a workaround by modifying "res_C" I made it also cloned, and
now it is restarted.


My Pacemaker 1.1.16-1.el6
System: CentOS 6

Regards,


​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20170413/7a578268/attachment.html>