From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Daniel Kral <d.kral@proxmox.com>
Subject: applied: [PATCH-SERIES ha-manager v2 0/2] fix #6084: allow dropping maintenance state with active HA resources
Date: Tue, 14 Jul 2026 17:24:25 +0200 [thread overview]
Message-ID: <178404266398.1262328.7083031298868390514.b4-ty@b4> (raw)
In-Reply-To: <20260709085632.62493-1-d.kral@proxmox.com>
On Thu, 09 Jul 2026 10:56:29 +0200, Daniel Kral wrote:
> changes v1 -> v2:
> - add extra context to comment in condition (as suggested by @Michael)
> - add R-b + T-b from Michael
>
> As reported in BZ #6804 [0], if a node held active HA resources, that
> could not be moved to any other node, while a node maintenance request
> has been placed and dropped again, the node's LRM would stay in
> maintenance state even though the maintenance mode was lifted.
>
> [...]
Applied, thanks!
[1/2] test: add maintenance test case with stuck HA resource
commit: f107bc91196e03a6125ef4a52c0aa255d05bd0c3
[2/2] fix #6084: lrm: allow dropping maintenance with active HA resources
commit: 858625dfce33ecf1a5ddcbca576fcb1ac90fbe9b
prev parent reply other threads:[~2026-07-14 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 8:56 [PATCH-SERIES ha-manager v2 0/2] fix #6084: allow dropping maintenance state with active HA resources Daniel Kral
2026-07-09 8:56 ` [PATCH ha-manager v2 1/2] test: add maintenance test case with stuck HA resource Daniel Kral
2026-07-09 8:56 ` [PATCH ha-manager v2 2/2] fix #6084: lrm: allow dropping maintenance with active HA resources Daniel Kral
2026-07-14 15:24 ` Thomas Lamprecht [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=178404266398.1262328.7083031298868390514.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=d.kral@proxmox.com \
--cc=pve-devel@lists.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