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 1B9331FF141 for ; Fri, 13 Feb 2026 17:09:54 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BE62EB6AE; Fri, 13 Feb 2026 17:10:41 +0100 (CET) From: Nicolas Frey To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs 3/3] pvecm: add notes about needing to remove QDevice when removing a node Date: Fri, 13 Feb 2026 17:09:56 +0100 Message-ID: <20260213160956.224162-4-n.frey@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260213160956.224162-1-n.frey@proxmox.com> References: <20260213160956.224162-1-n.frey@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.122 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: Y6ACIF5FWDWPQYBM4666RHZZK7EVS4HV X-Message-ID-Hash: Y6ACIF5FWDWPQYBM4666RHZZK7EVS4HV X-MailFrom: nfrey@miso.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: there was already an entry for this in the FAQ section later in the chapter, which could easily be overlooked. Signed-off-by: Nicolas Frey --- This came up when I was talking to @Friedrich about removing a cluster node and then not finding the part to link to for needing to remove the QDevice. IDK if notes are the proper way to link to this section here and whether duplicating them is OK. After the doc for removing a cluster node was recently split up (cc52fbaa15d9), I reckoned having it in each section would be fine pvecm.adoc | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/pvecm.adoc b/pvecm.adoc index 1ea3077..79f98b3 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -323,6 +323,10 @@ was also part of a xref:chapter_pveceph[Ceph] cluster. If Ceph was not installed on your node, you can simply ignore the steps that mention it. +NOTE: If your configuration contains a QDevice, you will need to remove it +before removing the cluster node, as outlined in the FAQ +xref:_adding_deleting_nodes_after_qdevice_setup[here]. + Prerequisites ~~~~~~~~~~~~~ @@ -377,7 +381,6 @@ Membership information 4 1 node4 (local) ---- - . Start by removing the node from the Ceph cluster, this consists of multiple steps: @@ -487,6 +490,10 @@ does not get accessed by multiple clusters. After setting up this storage, move all data and VMs from the node to it. Then you are ready to separate the node from the cluster. +NOTE: If your configuration contains a QDevice, you will need to remove it +before removing the cluster node, as outlined in the FAQ +xref:_adding_deleting_nodes_after_qdevice_setup[here]. + WARNING: Ensure that all shared resources are cleanly separated! Otherwise you will run into conflicts and problems. -- 2.47.3