all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Nicolas Frey <n.frey@proxmox.com>
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	[thread overview]
Message-ID: <20260213160956.224162-4-n.frey@proxmox.com> (raw)
In-Reply-To: <20260213160956.224162-1-n.frey@proxmox.com>

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 <n.frey@proxmox.com>
---
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




  parent reply	other threads:[~2026-02-13 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 16:09 [PATCH docs 0/3] rephrase and fix typos, add notes about QDevice removal Nicolas Frey
2026-02-13 16:09 ` [PATCH pve-docs 1/3] pveceph: fix typo Nicolas Frey
2026-02-13 16:09 ` [PATCH pve-docs 2/3] pvecm: improve phrasing and use `pve` variable Nicolas Frey
2026-02-13 16:09 ` Nicolas Frey [this message]
2026-02-16 19:16 ` applied: [PATCH docs 0/3] rephrase and fix typos, add notes about QDevice removal Thomas Lamprecht

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=20260213160956.224162-4-n.frey@proxmox.com \
    --to=n.frey@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal