Hi all, I do have a strange behaviour with HAv2 2.1.0 in the following situation:
* 2 nodes in cluster, all fine * 1 IP resource, works on it's own * 1 group consisting of 4 Filesystem resources * default-resource-stickiness = 50 * default-resource-failure-stickiness = -101 * there are two constraints ** one location preference for the group with score 100 for node1 ** and one colocation constraint stating that the IP resource and the group should run together Scenario: a) I bring IP resource up with setting target_role to started b) IP is up on node2 (by chance) c) Now I try to start the group (also by changing the target role): The resources in the group don't come up. Log is saying that there is no node where the stuff could be run. By the way: crm_verify -L -VV doesn't complain about anything. So, what I expected: * The group would come up on node1 (rule) * The colocation constraint would force the IP resource to migrate to node1 My questions: a) What's going on? b) Do I have a misunderstanding of the colocation constraint? c) Is the colocation constraint really symetrical? Or is it important what to set in the from-clause and to-clause? Best regards Andreas Mock _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
