manager: service start: make EWRONG_NODE a non-fatal error

traverse the usual error counting mechanisms, as then the
select_service_node helper either picks up the right node and it
starts there or it can trigger fencing of that.

Note, in practice this normally can only happen if the admin
butchered around in the node cluster state, but as we only select the
safe nodes from the configured groups, we should be safe in any case.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm
index 5fcabffe76bcb5f269292dc18b1ff9f5a9996fc6..70c66ffff6aab62a311d9a5f83806351efcd5b2e 100644 (file)
--- a/src/PVE/HA/Manager.pm
+++ b/src/PVE/HA/Manager.pm
@@ -773,7 +773,7 @@ sub next_state_started {
                    # store flag to indicate successful start - only valid while state == 'started'
                    $sd->{running} = 1;
 
-               } elsif ($ec == ERROR) {
+               } elsif ($ec == ERROR || $ec == EWRONG_NODE) {
 
                    delete $sd->{running};