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 790971FF0C0 for ; Wed, 18 Nov 2026 15:46:28 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 8A82F218D7; Wed, 18 Nov 2026 15:45:26 +0100 (CET) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH ha-manager v4 12/17] lrm: document and initialize LRM instance properties Date: Wed, 18 Nov 2026 15:44:57 +0100 Message-ID: <20261118144502.231134-13-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261118144502.231134-1-d.kral@proxmox.com> References: <20261118144502.231134-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795013119447 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.474 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: SH5M5WNTVBGBLSR3C2Q6KZ7NTGGM6I7R X-Message-ID-Hash: SH5M5WNTVBGBLSR3C2Q6KZ7NTGGM6I7R 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: The properties of service_status and node_status in the LRM blessed object reference are updated in the update_lrm_status() method in each work() iteration. No functional changes intended. Signed-off-by: Daniel Kral Reviewed-by: Michael Köppl Tested-by: Michael Köppl --- src/PVE/HA/LRM.pm | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/PVE/HA/LRM.pm b/src/PVE/HA/LRM.pm index 89844942..412ef0b2 100644 --- a/src/PVE/HA/LRM.pm +++ b/src/PVE/HA/LRM.pm @@ -41,6 +41,13 @@ sub new { mode => 'active', cluster_state_update => 0, active_idle_rounds => 0, + # service_status from manager_status in current work() iteration + # does contain all HA resources, users must filter for the assigned node + service_status => {}, + # node_status from manager_status in current work() iteration + # this is only used to check whether a fence for the node is requested + # see $PVE::HA::NodeStatus::valid_node_states for possible values + node_status => 'unknown', }, $class; $self->set_local_status({ state => 'wait_for_agent_lock' }); @@ -203,6 +210,14 @@ sub flush_lrm_status { return 1; } +=head3 $self->update_lrm_status() + +Updates the internal LRM properties from the current C. + +Returns 1 if the update was successful, otherwise returns undef. + +=cut + sub update_lrm_status { my ($self) = @_; -- 2.47.3