From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 973741FF141 for ; Tue, 19 May 2026 22:17:16 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4764311FF5; Tue, 19 May 2026 22:17:14 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Subject: applied: [PATCH-SERIES ha-manager 0/2] make idle LRMs resolve leftover moving HA resources while disarmed Date: Tue, 19 May 2026 22:11:18 +0200 Message-ID: <177922102935.2532338.3573199123091614034.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519143842.382324-1-d.kral@proxmox.com> References: <20260519143842.382324-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: 1779221784230 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: M2WDR3WRFSJKT2KNUHWDWSUKO7NWH7LB X-Message-ID-Hash: M2WDR3WRFSJKT2KNUHWDWSUKO7NWH7LB X-MailFrom: t.lamprecht@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: On Tue, 19 May 2026 16:38:34 +0200, Daniel Kral wrote: > As in patch message #2: > > If there are HA resources, which are in transient states that defer the > disarming process, but their LRMs are already in idle state and disarmed > mode, these LRMs will not properly resolve the transient states of these > HA resources as assumed by the HA Manager. > > [...] Applied, thanks! Squashed Fiona's naming nits (disarm_deferring) into 2/2, added a contract doc on the new Tools helper, and dropped the unused $target_node destructuring and !$current_node guard while at it. As I looked into this too a bit, and seemingly went for a different angle, I added a follow-up to also freeze non-deferred services on the deferred cycle, otherwise any LRM restart in the meantime (apt upgrade, manual restart) hangs in 'restart' mode waiting for an active_service_count going to zero that due to the deferred-mode CRM won't happen. Bumped to 5.2.4. [1/2] test: add disarm test cases for idle lrms with transient ha resources commit: 54497ae43d5bdb3842eb6f32e0642da9deb7cf5b [2/2] make idle LRMs resolve leftover moving HA resources while disarmed commit: 9917559d01e60cc55622102bef2b8f5d87892d33