From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 38EC11FF141 for ; Tue, 19 May 2026 16:47:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9AAF7B42E; Tue, 19 May 2026 16:47:27 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 19 May 2026 16:47:23 +0200 Message-Id: Subject: Re: [PATCH-SERIES ha-manager 0/2] make idle LRMs resolve leftover moving HA resources while disarmed From: "Daniel Kral" To: "Daniel Kral" , X-Mailer: aerc 0.21.0-136-gdb9fe9896a79-dirty References: <20260519143842.382324-1-d.kral@proxmox.com> In-Reply-To: <20260519143842.382324-1-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779202029520 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.075 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: ETYDTPII2OPRR4OADCP75XK6RXL6UOUO X-Message-ID-Hash: ETYDTPII2OPRR4OADCP75XK6RXL6UOUO 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: On Tue May 19, 2026 at 4:38 PM CEST, 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. > > For HA resources, which are still moving, this makes the HA Manager > stuck in a loop, which tries to defer the disarming process to wait for > a LRM response for these moving HA resources, which will never come as > the LRM is idle. > > Therefore allow the LRM to become active in disarm mode if there are any > HA resources on the LRM's node, which are in any of these transient > states, and make sure that the LRM only processes the disarm-deferring > HA resources while the LRM is active. Sorry, forgot to add a this trailer to the series (can b4 pickup these trailers as well?): Reported-by: Max R. Carrara