From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Michael Köppl" <m.koeppl@proxmox.com>
Subject: [pve-devel] applied: [PATCH ha-manager v3 1/2] fix #6613: update rules containing the resource to be deleted
Date: Fri, 14 Nov 2025 15:09:19 +0100 [thread overview]
Message-ID: <176312935733.3907150.4368787717586309899.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250930145848.263162-2-m.koeppl@proxmox.com>
On Tue, 30 Sep 2025 16:58:38 +0200, Michael Köppl wrote:
> If the purge param is set, the resource that is deleted is also removed
> from any rules referencing it. In the case that a resource is removed
> that is also the last resource in a rule, the rule is also removed if
> the purge option is enabled. This avoids rules remaining in the rules
> config if their resources no longer exist.
>
>
> [...]
Applied, thanks!
This one shouldn't be to hard to add coverage for in our test system, but no
high priority now.
[1/2] fix #6613: update rules containing the resource to be deleted
commit: 8102199f9e2377c73353c99d581dc72a8e3d6726
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-14 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 14:58 [pve-devel] [PATCH container/docs/ha-manager/manager/widget-toolkit/qemu-server v3 00/11] fix #6613: update HA rules upon resource deletion Michael Köppl
2025-09-30 14:58 ` [pve-devel] [PATCH ha-manager v3 1/2] fix #6613: update rules containing the resource to be deleted Michael Köppl
2025-11-14 14:09 ` Thomas Lamprecht [this message]
2025-09-30 14:58 ` [pve-devel] [PATCH ha-manager v3 2/2] api: add purge parameter for resource deletion Michael Köppl
2025-11-14 14:09 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH qemu-server v3 1/1] fix #6613: pass purge param to delete_service_from_config Michael Köppl
2025-11-13 22:51 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH container " Michael Köppl
2025-09-30 14:58 ` [pve-devel] [PATCH widget-toolkit v3 1/4] window: refactor construction of SafeDestroy items Michael Köppl
2025-10-02 11:35 ` Daniel Kral
2025-11-10 16:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH widget-toolkit v3 2/4] window: introduce dangerous parameter to SafeDestroy Michael Köppl
2025-11-10 16:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH widget-toolkit v3 3/4] window: make buttons in SafeDestroy configurable Michael Köppl
2025-11-10 16:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH widget-toolkit v3 4/4] window: add more general base dialog, make SafeDestroy concrete Michael Köppl
2025-11-10 16:48 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-30 14:58 ` [pve-devel] [PATCH manager v3 1/2] ui: add ConfirmRemoveResource window Michael Köppl
2025-09-30 14:58 ` [pve-devel] [PATCH manager v3 2/2] ui: use ConfirmRemoveResource window for removing resources Michael Köppl
2025-09-30 14:58 ` [pve-devel] [PATCH docs v3 1/1] add notes about effects of purge flag for resource and guest removal Michael Köppl
2025-10-02 11:18 ` [pve-devel] [PATCH container/docs/ha-manager/manager/widget-toolkit/qemu-server v3 00/11] fix #6613: update HA rules upon resource deletion Daniel Kral
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=176312935733.3907150.4368787717586309899.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.koeppl@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