all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Rusovac <d.rusovac@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Thomas Skinner <thomas@atskinner.net>
Subject: [PATCH pve-docs v4 4/4] ha-manager: maintenance mode: mention web ui menu
Date: Fri, 13 Nov 2026 16:26:20 +0100	[thread overview]
Message-ID: <20261113152620.2662417-5-d.rusovac@proxmox.com> (raw)
In-Reply-To: <20261113152620.2662417-1-d.rusovac@proxmox.com>

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 <thomas@atskinner.net>
Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>
---

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





  parent reply	other threads:[~2026-11-13 15:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 15:26 [PATCH-SERIES docs/ha-manager/manager v4 0/4] fix #6144: add api and ui for node maintenance mode Dominik Rusovac
2026-11-13 15:26 ` [PATCH pve-manager v4 1/4] api: nodes: add endpoint to set " Dominik Rusovac
2026-11-16 11:57   ` Daniel Kral
2026-11-17  8:58     ` Dominik Rusovac
2026-11-17  9:21       ` Daniel Kral
2026-11-17  9:40         ` Dominik Rusovac
2026-11-13 15:26 ` [PATCH pve-manager v4 2/4] fix #6144: ui: ha: status: allow toggling " Dominik Rusovac
2026-11-17  9:07   ` Daniel Kral
2026-11-17 11:02     ` Dominik Rusovac
2026-11-13 15:26 ` [PATCH pve-ha-manager v4 3/4] api: status: report node maintenance request for lrm entries Dominik Rusovac
2026-11-16 12:02   ` Daniel Kral
2026-11-13 15:26 ` Dominik Rusovac [this message]
2026-11-19 10:05 ` [PATCH-SERIES docs/ha-manager/manager v4 0/4] fix #6144: add api and ui for node maintenance mode Dominik Rusovac

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261113152620.2662417-5-d.rusovac@proxmox.com \
    --to=d.rusovac@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=thomas@atskinner.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal