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 CD7401FF137 for ; Tue, 03 Feb 2026 15:52:42 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5365921F25; Tue, 3 Feb 2026 15:53:13 +0100 (CET) From: Hannes Duerr To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs 2/2] add note that when removing a cluster node, it is not removed from HA rules. Date: Tue, 3 Feb 2026 15:52:32 +0100 Message-ID: <20260203145232.142544-2-h.duerr@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260203145232.142544-1-h.duerr@proxmox.com> References: <20260203145232.142544-1-h.duerr@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770130284038 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.071 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: YHZEBTUU3AGBZ3OV6ZWDNQUVYEKILX7M X-Message-ID-Hash: YHZEBTUU3AGBZ3OV6ZWDNQUVYEKILX7M X-MailFrom: h.duerr@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: Signed-off-by: Hannes Duerr --- pvecm.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index 1904a00..4db479b 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -420,6 +420,10 @@ NOTE: It is possible that you will receive an error message stating signify an actual failure in the deletion of the node, but rather a failure in Corosync trying to kill an offline node. thus, it can be safely ignored. ++ +NOTE: Removing the cluster node does not automatically remove the node +from existing high availability rules. You must do this manually after +deleting the cluster node. . After the node got removed the configuration files of the removed node will still reside in '/etc/pve/nodes/node4' in the cluster -- 2.47.3