From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id D9C741FF0B6 for ; Thu, 12 Nov 2026 17:33:18 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id EE7BC217BF; Thu, 12 Nov 2026 17:32:15 +0100 (CET) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH ha-manager v2 10/16] lrm: rename update_service_status to update_lrm_status Date: Thu, 12 Nov 2026 17:31:09 +0100 Message-ID: <20261112163113.294302-13-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261112163113.294302-3-d.kral@proxmox.com> References: <20261112163113.294302-3-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794501128103 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.619 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: U4LEPQPWLGW6SBOEOWCCI2MVZXXHAZLF X-Message-ID-Hash: U4LEPQPWLGW6SBOEOWCCI2MVZXXHAZLF X-MailFrom: d.kral@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: update_lrm_status() is more fitting than update_service_status() here as the internal LRM state that is updated by the information provided by manager status does affect the LRM's behavior (mode and node_status) and not only the LRM's behavior for its HA resources (service_status). Signed-off-by: Daniel Kral --- src/PVE/HA/LRM.pm | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/src/PVE/HA/LRM.pm b/src/PVE/HA/LRM.pm index 8cc2e57c..fda9067a 100644 --- a/src/PVE/HA/LRM.pm +++ b/src/PVE/HA/LRM.pm @@ -203,7 +203,7 @@ sub flush_lrm_status { return 1; } -sub update_service_status { +sub update_lrm_status { my ($self) = @_; my $haenv = $self->{haenv}; @@ -217,7 +217,6 @@ sub update_service_status { my $nodename = $haenv->nodename(); $self->{node_status} = $ms->{node_status}->{$nodename} || 'unknown'; - # FIXME: method name is a bit confusing for doing this, either rename or move if (!$self->{shutdown_request}) { my $request = $ms->{node_request}->{$nodename} // {}; if ($request->{maintenance}) { @@ -371,7 +370,7 @@ sub work { my $status = $self->get_local_status(); my $state = $status->{state}; - $self->update_service_status(); + $self->update_lrm_status(); my $fence_request = $self->is_fence_requested(); @@ -502,7 +501,7 @@ sub work { # if we could not get the current service status there's no point # in doing anything, try again next round. - return if !$self->update_service_status(); + return if !$self->update_lrm_status(); if ($self->{shutdown_request}) { @@ -601,7 +600,7 @@ sub work { } elsif ($state eq 'maintenance') { my $startime = $haenv->get_time(); - return if !$self->update_service_status(); + return if !$self->update_lrm_status(); # wait until all active services moved away my $service_count = $self->active_service_count(); -- 2.47.3