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 EE4361FF141 for ; Mon, 30 Mar 2026 15:40:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D899D31A4C; Mon, 30 Mar 2026 15:40:25 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs 3/4] ha-manager: add disarming HA section Date: Mon, 30 Mar 2026 15:40:17 +0200 Message-ID: <20260330134019.419391-4-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: 1774877965704 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.125 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: LATEKQVDULZUPSPLO2ZWZB7QGVBQGYSO X-Message-ID-Hash: LATEKQVDULZUPSPLO2ZWZB7QGVBQGYSO 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 --- ha-manager.adoc | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 68fb7d1..3c97a2d 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1086,6 +1086,37 @@ this is not the case the update process can take too long which, in the worst case, may result in a reset triggered by the watchdog. +[[ha_manager_cluster_maintenance]] +Cluster-wide Maintenance +------------------------ + +If a cluster has HA-resources then one has to be careful during a maintenance +that involves multiple nodes or when performing configuration changes on +multiple node, as connectivity issues on the Corosync network can result in one +or more nodes fencing. One common example is when editing Corosync's +configuration as the changes will be picked up by all cluster nodes and any +configuration error can lead to nodes potentially fencing. In this scenario one +can temporarily disarm HA in order to release the watchdogs in the cluster. + +You can disarm and arm HA using the ha-manager CLI tool. + +.Disarming HA +---- +# ha-manager crm-command disarm-ha +---- + +.Arming HA +---- +# ha-manager crm-command arm-ha +---- + +There are two possible resource modes for disarming HA: + +- `freeze`: new commands and state changes are not applied. +- `ignore`: resources are removed from HA tracking and can be managed as if they + were not HA managed. + + [[ha_manager_node_maintenance]] Single Node Maintenance ----------------------- -- 2.47.3