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 ED1BA1FF13B for ; Wed, 25 Mar 2026 13:07:06 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D8BFA16737; Wed, 25 Mar 2026 13:07:25 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Thomas Lamprecht Subject: applied: [PATCH ha-manager v2 0/4] fix #2751: implement disarm/arm HA for safer cluster maintenance Date: Wed, 25 Mar 2026 13:06:26 +0100 Message-ID: <177444038297.2818201.14301311718427139801.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260321234350.2158438-1-t.lamprecht@proxmox.com> References: <20260321234350.2158438-1-t.lamprecht@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: 1774440393978 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.011 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: VLZU7E5HT6IDZP2JICEFKDWUPGIWXOIX X-Message-ID-Hash: VLZU7E5HT6IDZP2JICEFKDWUPGIWXOIX 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 Sun, 22 Mar 2026 00:42:49 +0100, Thomas Lamprecht wrote: > The biggest change compared to v1 is how ignore mode handles the service > status: instead of clearing it entirely, the relevant parts of service > status are now preserved across the disarm/arm cycle. This allows > runtime state like maintenance_node to survive, so services correctly > migrate back to their original node after maintenance ends, even if the > disarm happened while maintenance was active. Thanks @Dominik R. for > noticing this. > > [...] Applied, with the DRY style issue that Dominik spotted squashed in (thanks!) [1/4] sim: hardware: add manual-migrate command for ignored services commit: be22651cf9756d2e02bca428ab708fc3fedcaa9b [2/4] api: status: add fencing status entry with armed/standby state commit: 2d143acf0289badaa60f5222af0f260f0efc55ac [3/4] fix #2751: implement disarm-ha and arm-ha for safe cluster maintenance commit: d9714e7047dda84b5bd901d39471944ef1d4fe98 [4/4] api: status: add disarm-ha and arm-ha endpoints and CLI wiring commit: 3f2e82674b86de92e4526048c1356aec54e527f5