* [PATCH pve-docs] cluster: fix reference to faq section
@ 2026-02-18 5:57 Hannes Laimer
0 siblings, 0 replies; only message in thread
From: Hannes Laimer @ 2026-02-18 5:57 UTC (permalink / raw)
To: pve-devel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-02-18 5:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-02-18 5:57 [PATCH pve-docs] cluster: fix reference to faq section Hannes Laimer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox