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 7DD571FF0E0 for ; Thu, 09 Jul 2026 11:05:58 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id D25D92145B; Thu, 09 Jul 2026 11:05:57 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 09 Jul 2026 11:05:53 +0200 Message-Id: To: "Daniel Kral" , Subject: superseded: [PATCH-SERIES ha-manager 0/2] fix #6084: allow dropping maintenance state with active HA resources From: "Daniel Kral" X-Mailer: aerc 0.21.0-147-g43ac7b685014-dirty References: <20260708084205.69947-1-d.kral@proxmox.com> In-Reply-To: <20260708084205.69947-1-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783587943863 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.011 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) 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: JJSIVSIVYS3HGYYOC3OWPZVLNOIJEUA6 X-Message-ID-Hash: JJSIVSIVYS3HGYYOC3OWPZVLNOIJEUA6 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: Superseded-by: https://lore.proxmox.com/pve-devel/20260709085632.62493-1-d.= kral@proxmox.com/ On Wed Jul 8, 2026 at 10:42 AM CEST, Daniel Kral wrote: > As reported in BZ #6804 [0], if a node held active HA resources, that > could not be moved to any other node, while a node maintenance request > has been placed and dropped again, the node's LRM would stay in > maintenance state even though the maintenance mode was lifted. > > This small patch series fixes the issue by also allowing LRMs with > active assigned HA resources to be moved out of maintenance state again. > > [0] https://bugzilla.proxmox.com/show_bug.cgi?id=3D6084