I have a linkup resource that can only run on node with external eth connection present. Linkup resource fails as soon as node looses external connectivity and fails over to another node. Then it tries to start there. It starts successfully if node has external connection. I want it to attract serverIP resource to that node. The idea in general is that linkup tries to start on several nodes until either it discovers that no nodes have external link or finds one and then moves serverIP there. I create a co-location constraint from the linkup RA "start" and remove this constraint from "stop".
The problem is: linkup fails on A and fails over to B creates a constraint with INFINITY to co-locate with serverIP in "start", "start" returns OCF_SUCCES as soon as constraint is created HA tries to start linkup again on that node where it has failed ( because serverIP is still there ), obviously "start" fails and I have linkup and serverIP run on B but INFINITY fail counter for A and "start_on_A" in failed actions. So linkup will never run on A again until I clear it in LRM by crm_resource -C. Does anybody know, what's the reason of such behavior and is there a workaround? I supposed that serverIP should follow the linkup when the constraint appears... but HA prefers to restart linkup on node where it has just failed. This looks strange for me. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
