From: "Dominik Rusovac" <d.rusovac@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH ha-manager 0/3] fix #2751: implement disarm/arm HA for safer cluster maintenance
Date: Tue, 17 Mar 2026 13:35:45 +0100 [thread overview]
Message-ID: <DH528F7Q9W5J.JQQZHVE7AII8@proxmox.com> (raw)
In-Reply-To: <20260309220128.973793-1-t.lamprecht@proxmox.com>
Thank you for digging this out!
On Mon Mar 9, 2026 at 10:57 PM CET, Thomas Lamprecht wrote:
[snip]
> TBD:
> - more in-depth (real-world!) testing
In a real cluster, consisting of:
- node1 with 2 ha-resources;
- node2 with 2 ha-resources; and
- node3 with 0 ha-resources,
the following has been tested:
- with resource mode 'freeze':
- CRM master takeover while HA stack is fully disarmed (OK)
- new commands are not applied: (OK)
- stop node (OK)
- enable node-maintenance (OK)
- disable node-maintenance (OK)
NOTE: it is possible to disable node-maintenance in
disarmed state. The disable command is applied
upon re-arming, accordingly services are moved
back upon re-arming, could this be critical?
- relocate ha-resource (OK)
- migrate ha-resource (OK)
- state changes are not applied (OK)
NOTE: it is possible to change the state, but the
change will only be applied upon re-arming
- services stay in their current state (OK)
- HA stack does not react to failures (OK)
- stop some node (OK)
- with resource mode 'ignore':
- manually starting, stopping, migrating services (OK)
> - UI integration
I started drafting something. UI integration requires protected
endpoints.
> - docs (got something started here, but can be finished once this is
[snip]
I found no major flaws, neither in the present approach nor in the
implementation. Just some minor things, constituted by inline comments
across this series' patches. Consider this series modulo:
- prohibit disarming with resource mode 'ignore' if at least one node
is in maintenance mode
- make endpoints protected
Reviewed-by: Dominik Rusovac <d.rusovac@proxmox.com>
Tested-by: Dominik Rusovac <d.rusovac@proxmox.com>
prev parent reply other threads:[~2026-03-17 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 21:57 Thomas Lamprecht
2026-03-09 21:57 ` [PATCH ha-manager 1/3] api: status: add fencing status entry with armed/standby state Thomas Lamprecht
2026-03-09 21:57 ` [PATCH ha-manager 2/3] fix #2751: implement disarm-ha and arm-ha for safe cluster maintenance Thomas Lamprecht
2026-03-17 12:36 ` Dominik Rusovac
2026-03-09 21:57 ` [PATCH ha-manager 3/3] api: status: add disarm-ha and arm-ha endpoints and CLI wiring Thomas Lamprecht
2026-03-17 12:47 ` Dominik Rusovac
2026-03-17 12:35 ` Dominik Rusovac [this message]
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=DH528F7Q9W5J.JQQZHVE7AII8@proxmox.com \
--to=d.rusovac@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox