Hello, I have a primitive resource (in my case, a IPaddr2 simple failover IP). Now I happen to find the resource running on both of the members of the HA cluster. Well, pacemaker says he has started it only on one of the nodes, but the IP address which is managed by this resource is configured on both nodes of the cluster.
Since I don't know what strange events may have lead to this situation (perhaps it was a manual manipulation), I created the following testcase to investigate this: configure a cluster, add some failover IP address primitive resource, let pacemaker start in on one host. Configure this IP address manually on the other host. Hope that pacemaker will detect it and react somehow (stop the resource, or do some stonith, or whatever). But even with some monitoring op defined, pacemaker seems only to check that the resource is running on the host it is scheduled for, and it does not check that the resource is not running on the host where it should not run. (I verified that the resource agent itself determines the status correctly, i.e. on the started resource, the monitoring action returns 0, on the stopped resource, it returns 7.) Is this observation correct? Is this the expected behavior? Is it possible to configure the resource such that it is checked that the resource is stopped where it is expected to be stopped? Regards Dominik _______________________________________________ Pacemaker mailing list: [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
