Hello, suppose I have group of resources named G1 and a resource named R2. I define an order R2 after G1 and a colocation constraint of -inf so that they run on different nodes (2 nodes overall). At runtime I have G1 on node1 and R2 on node2, correctly. I do a move of G1, so that I would have at the end G1 on node2 and R2 on node1.
But suppose node1 doesn' t satisfy requirements for running R2 (for example a file system without the mount point defined on node1). Is it expected behaviour that I get: - R2 stops correctly on node2 - G1 starts correctly on node2 - R2 then, based on constraint and order, tries to start on node1 but fails - G1 too goes in stopped status, so that I now have both G1 and R2 stopped Other questions: - If instead I had suddenly run a move and then unmove of G1, would it have tried to run on node1 again or is it the failure itself of R2 to cause the stop of G1 too? - Is there a way to tell that even if R2 fails, then don't impact on G1? - Is there a way to run a move command that automatically does an unmove (what normally is called a relocation of a service, which in general doesn't imply to mark the node as unable to get the resource again back). Thanks for clarifications Gianluca _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
