all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs] cluster: fix reference to faq section
Date: Wed, 18 Feb 2026 06:57:34 +0100	[thread overview]
Message-ID: <20260218055734.35887-1-h.laimer@proxmox.com> (raw)

Since `scan-adoc-refs` only registers explicit refs, we can't use
an auto-id to reference something.

Fixes: 7780a53b ("pvecm: add notes about needing to remove QDevice when removing a node")
Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
 pvecm.adoc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 79f98b3..cbeffa1 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -325,7 +325,7 @@ 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].
+xref:adding_deleting_nodes_after_qdevice_setup[here].
 
 Prerequisites
 ~~~~~~~~~~~~~
@@ -492,7 +492,7 @@ 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].
+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.
@@ -1283,6 +1283,7 @@ For clusters with an even node count, there are no negative implications when
 using a QDevice. If it fails to work, it is the same as not having a QDevice
 at all.
 
+[[adding_deleting_nodes_after_qdevice_setup]]
 Adding/Deleting Nodes After QDevice Setup
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-- 
2.47.3





                 reply	other threads:[~2026-02-18  5:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260218055734.35887-1-h.laimer@proxmox.com \
    --to=h.laimer@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