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 7456A1FF138 for ; Wed, 18 Feb 2026 06:57:14 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1DCE0120A9; Wed, 18 Feb 2026 06:58:12 +0100 (CET) From: Hannes Laimer 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 Message-ID: <20260218055734.35887-1-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771394248291 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.060 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: E5GRAY75XFPLAYJY4OAP3INRSP4N6I3D X-Message-ID-Hash: E5GRAY75XFPLAYJY4OAP3INRSP4N6I3D X-MailFrom: h.laimer@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: 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 --- 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