Hello, if a resource has encounters a start error with rc=5 "not installed" the stop action is not skipped before a restart is tried.
Typically in such a situation the stop will also fail with the same error and the node will be fenced ... even worse there is a good change this happens on all remaining nodes e.g. if there is a typo in a parameter. I would expect the cluster to skip the stop action after a "not installed" start failure followed by a start retry on a different node. So ... is this a feature or a bug? ;-) Regards, Andreas _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
