From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 5DFD41FF0B7 for ; Fri, 13 Nov 2026 16:26:42 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 6C15F2171E; Fri, 13 Nov 2026 16:26:31 +0100 (CET) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v4 4/4] ha-manager: maintenance mode: mention web ui menu Date: Fri, 13 Nov 2026 16:26:20 +0100 Message-ID: <20261113152620.2662417-5-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261113152620.2662417-1-d.rusovac@proxmox.com> References: <20261113152620.2662417-1-d.rusovac@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794583586136 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.027 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: LQS2U2FSNUYCL3DFLFLNF2Z4CES46GZU X-Message-ID-Hash: LQS2U2FSNUYCL3DFLFLNF2Z4CES46GZU X-MailFrom: d.rusovac@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 CC: Thomas Skinner X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: maintenance mode can now also be enabled/disabled from the HA status panel describe where to find it and that it cannot be enabled while HA is disarmed fix the "enabled or disable" typo in the rewritten sentence Originally-by: Thomas Skinner Signed-off-by: Dominik Rusovac --- Notes: changes since v3: * reword commit subject and body * condense the ui instructions into one paragraph * use the final menu name and mention the disarm restriction ha-manager.adoc | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 95ab799..4962bb9 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1199,8 +1199,10 @@ During each migration, the original node will be recorded in the HA managers' state, so that the service can be moved back again automatically once the maintenance mode is disabled and the node is back online. -Currently you can enabled or disable the maintenance mode using the ha-manager -CLI tool. +You can enable or disable the maintenance mode using the web interface or the +`ha-manager` CLI tool. In the web interface, select the `lrm` entry of the node +in the status panel under __Datacenter -> HA__ and use the *Node Maintenance* +menu. Maintenance mode cannot be enabled while HA is disarmed. .Enabling maintenance mode for a node ---- @@ -1225,8 +1227,8 @@ out for a log line like: `pve-ha-lrm[PID]: watchdog closed (disabled)` to know when the node finished its transition into the maintenance mode. NOTE: The manual maintenance mode is not automatically deleted on node reboot, -but only if it is either manually deactivated using the `ha-manager` CLI or if -the manager-status is manually cleared. +but only if it is either manually deactivated or if the manager-status is +manually cleared. .Disabling maintenance mode for a node ---- @@ -1234,8 +1236,9 @@ the manager-status is manually cleared. ---- The process of disabling the manual maintenance mode is similar to enabling it. -Using the `ha-manager` CLI command shown above will queue a CRM command that, -once processed, marks the respective LRM node as available again. +Using the web interface or the `ha-manager` CLI command shown above will queue a +CRM command that, once processed, marks the respective LRM node as available +again. If you deactivate the maintenance mode, all services that were on the node when the maintenance mode was activated will be moved back. -- 2.47.3