From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 8F8E51FF141 for ; Mon, 30 Mar 2026 15:40:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6E57231F2C; Mon, 30 Mar 2026 15:40:56 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs 4/4] corosync config: add xref to disarming HA section Date: Mon, 30 Mar 2026 15:40:18 +0200 Message-ID: <20260330134019.419391-5-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260330134019.419391-1-m.sandoval@proxmox.com> References: <20260330134019.419391-1-m.sandoval@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1774877965804 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.126 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 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: JNT64TUCTGNHL37Z5AGR5U7MJB3UMEVE X-Message-ID-Hash: JNT64TUCTGNHL37Z5AGR5U7MJB3UMEVE X-MailFrom: m.sandoval@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: Signed-off-by: Maximiliano Sandoval --- pvecm.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index a48b18c..e4330ae 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1377,6 +1377,12 @@ corosync service via: systemctl restart corosync ---- +Note that restarting the Corosync service on a cluster with HA resources might +lead to the node fencing if the service does not come back up properly. This can +happen, for example, if the new version of the configuration has a typo or +errors in general. xref:ha_manager_cluster_maintenance[Cluster-wide Maintenance] +for more details. + On errors, check the troubleshooting section below. Changing the Token Coefficient -- 2.47.3