lrm: also check CRM node-status for determining fence-request

[pve-ha-manager.git] / src / PVE / HA / LRM.pm

diff --git a/src/PVE/HA/LRM.pm b/src/PVE/HA/LRM.pm
index 1ba2038fb80d544eef8242b28c61ff0c5a8b315c..86d0a34ffb0e93508611779cb85871c4c508499e 100644 (file)
--- a/src/PVE/HA/LRM.pm
+++ b/src/PVE/HA/LRM.pm
@@ -186,6 +186,8 @@ sub update_service_status {
        return undef;
     } else {
        $self->{service_status} = $ms->{service_status} || {};
+       my $nodename = $haenv->nodename();
+       $self->{node_status} = $ms->{node_status}->{$nodename} || 'unknown';
        return 1;
     }
 }
@@ -242,12 +244,13 @@ sub is_fence_requested {
     my ($self) = @_;
 
     my $haenv = $self->{haenv};
+
     my $nodename = $haenv->nodename();
     my $ss = $self->{service_status};
 
     my $fenced_services = PVE::HA::Tools::count_fenced_services($ss, $nodename);
 
-    return $fenced_services;
+    return $fenced_services || $self->{node_status} eq 'fence';
 }
 
 sub active_service_count {