From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container/docs/ha-manager/manager/qemu-server 0/7] fix #6613: update HA rules upon resource deletion
Date: Wed, 17 Sep 2025 13:53:09 +0200 [thread overview]
Message-ID: <20250917115316.131793-1-m.koeppl@proxmox.com> (raw)
This patch series aims to fix #6613 [0]. Although an implementation was
proposed in the past, it was not applied since it was unclear how to
handle the case where the removed resource is the last resource in a
rule.
The approach in this patch series is the following:
- With the purge param activated (default), the
resource is removed from any rule referencing it.
- Without the purge param, rules are left untouched, making the removal
of resources from rules "opt-out", as was suggested in the previous
implementation [1].
- If the resource was the last resource in the rule *and* the purge
param is set, the rule will also be deleted.
- For guest destruction, the "Purge from job configurations" option will
also set the purge parameter for removing the HA resource
- The purge param is set by default for resource removal in the GUI and
CLI
After some back-and-forth, I settled in this approach as the most
intuitive and transparent. Alternative approaches considered were the
following:
- Updating rules even without the purge flag set, but failing and
showing an error to the user if a rule would be deleted, prompting the
user to enable the purge flag. This approach seems to be to
restrictive and IMO doesn't add any UX value.
- By default not setting the purge flag. This would by default leave
"zombie" rules with non-existent resources. This is IMO intransparent
if it happens by default. Users might be removing resources, not even
knowing they're leaving behind rules that still reference said
resources.
But I'm also asking for input here if someone has a different opinion or
suggestions for alternative approaches.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=6613
[1] https://lore.proxmox.com/pve-devel/c004b755-ba3c-46cd-b559-ee2c131d97fc@proxmox.com
pve-ha-manager:
Michael Köppl (2):
fix #6613: update rules containing the resource to be deleted
api: add purge parameter for resource deletion
src/PVE/API2/HA/Resources.pm | 10 +++++++++-
src/PVE/HA/Config.pm | 15 ++++++++++++++-
2 files changed, 23 insertions(+), 2 deletions(-)
qemu-server:
Michael Köppl (1):
fix #6613: pass purge param to delete_service_from_config
src/PVE/API2/Qemu.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
pve-container:
Michael Köppl (1):
fix #6613: pass purge param to delete_service_from_config
src/PVE/API2/LXC.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pve-manager:
Michael Köppl (2):
ui: add SafeDestroyResource window
ui: use SafeDestroyResource window for removing resources
www/manager6/Makefile | 1 +
www/manager6/ha/Resources.js | 17 +++++++++---
www/manager6/window/SafeDestroyResource.js | 32 ++++++++++++++++++++++
3 files changed, 46 insertions(+), 4 deletions(-)
create mode 100644 www/manager6/window/SafeDestroyResource.js
pve-docs:
Michael Köppl (1):
add notes about effects of purge flag for resource and guest removal
ha-manager.adoc | 4 ++++
pct.adoc | 3 +++
qm.adoc | 3 +++
3 files changed, 10 insertions(+)
Summary over all repositories:
10 files changed, 83 insertions(+), 8 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-17 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 11:53 Michael Köppl [this message]
2025-09-17 11:53 ` [pve-devel] [PATCH ha-manager 1/2] fix #6613: update rules containing the resource to be deleted Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH ha-manager 2/2] api: add purge parameter for resource deletion Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH qemu-server 1/1] fix #6613: pass purge param to delete_service_from_config Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH container " Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH manager 1/2] ui: add SafeDestroyResource window Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH manager 2/2] ui: use SafeDestroyResource window for removing resources Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH docs 1/1] add notes about effects of purge flag for resource and guest removal Michael Köppl
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=20250917115316.131793-1-m.koeppl@proxmox.com \
--to=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