[ClusterLabs] cloned resources ordering and remote nodes problem

Ken Gaillot kgaillot at redhat.com
Tue May 9 15:33:41 EDT 2017

On 04/13/2017 08:49 AM, Radoslaw Garbacz wrote:
> 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

I haven't been able to reproduce this. Can you attach a configuration
file that exhibits the problem?

More information about the Users mailing list