From: Hannes Duerr <h.duerr@proxmox.com>
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 [thread overview]
Message-ID: <20260203145232.142544-2-h.duerr@proxmox.com> (raw)
In-Reply-To: <20260203145232.142544-1-h.duerr@proxmox.com>
Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
---
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
prev parent reply other threads:[~2026-02-03 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 14:52 [PATCH pve-docs 1/2] restructure "remove a cluster node" section Hannes Duerr
2026-02-03 14:52 ` Hannes Duerr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260203145232.142544-2-h.duerr@proxmox.com \
--to=h.duerr@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox