[Pacemaker] start error because "not installed" - stop fails with "not installed" - stonith

[Andreas Kurz]

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