From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-manager v3 16/16] ui: guest destroy: add control for dangling IPSet references
Date: Fri, 25 Sep 2026 11:42:30 +0200 [thread overview]
Message-ID: <20260925094230.844917-17-a.bied-charreton@proxmox.com> (raw)
In-Reply-To: <20260925094230.844917-1-a.bied-charreton@proxmox.com>
Destroying a guest releases its IPAM entries, so the auto-generated
'guest-ipam-<vmid>' IPSet disappears with it. Rules referencing that
IPSet do not resolve anymore and are silently dropped from the
generated ruleset.
Add the shared selector to the destroy dialog, so those rules can be
disabled or deleted along with the guest, next to a hint linking to
the SDN firewall integration documentation. 'keep' remains the
default, matching the API.
The 'note' config only renders a single hint, so it is replaced by
two display fields among the additional items.
Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
www/manager6/window/SafeDestroyGuest.js | 44 ++++++++++++++++++++++++-
1 file changed, 43 insertions(+), 1 deletion(-)
diff --git a/www/manager6/window/SafeDestroyGuest.js b/www/manager6/window/SafeDestroyGuest.js
index 45b277e5..45099342 100644
--- a/www/manager6/window/SafeDestroyGuest.js
+++ b/www/manager6/window/SafeDestroyGuest.js
@@ -32,7 +32,46 @@ Ext.define('PVE.window.SafeDestroyGuest', {
},
],
- note: gettext('Referenced disks will always be destroyed.'),
+ initComponent: function () {
+ let me = this;
+
+ let helpLink = Ext.htmlEncode(Proxmox.Utils.get_help_link('pvesdn_firewall_integration'));
+ let helpLabel = Ext.htmlEncode(gettext('this guest\'s auto-generated IPSet'));
+ let refsHint = Ext.String.format(
+ gettext('Firewall rules referencing {0} will no longer resolve.'),
+ `<a target="_blank" href="${helpLink}">${helpLabel}</a>`,
+ );
+
+ me.additionalItems = [
+ // build fresh array per instance, pushing would append every time the dialog is opened
+ ...me.additionalItems,
+ {
+ xtype: 'displayfield',
+ userCls: 'pmx-hint',
+ value: gettext('Referenced disks will always be destroyed.'),
+ },
+ {
+ xtype: 'displayfield',
+ userCls: 'pmx-hint',
+ value: refsHint,
+ },
+ {
+ xtype: 'pveFirewallDanglingReferences',
+ reference: 'firewallDanglingReferencesButton',
+ value: 'keep',
+ labelWidth: 200,
+ keepTip: gettext(
+ 'Keep referencing rules. They are dropped from the generated ruleset and shown as invalid until a guest with the same VMID is recreated.',
+ ),
+ disableTip: gettext(
+ 'Disable referencing rules, keeping them in the firewall configuration.',
+ ),
+ dropTip: gettext('Delete referencing rules.'),
+ },
+ ];
+
+ me.callParent();
+ },
getParams: function () {
let me = this;
@@ -43,6 +82,9 @@ Ext.define('PVE.window.SafeDestroyGuest', {
let destroyUnreferencedCheckbox = me.lookupReference('destroyUnreferencedCheckbox');
me.params['destroy-unreferenced-disks'] = destroyUnreferencedCheckbox.checked ? 1 : 0;
+ let danglingRefs = me.lookupReference('firewallDanglingReferencesButton');
+ me.params['dangling-ipset-references'] = danglingRefs.getValue();
+
return me.callParent();
},
});
--
2.47.3
next prev parent reply other threads:[~2026-09-25 9:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 9:42 SPAM: [PATCH container/firewall/manager/network/qemu-server v3 00/16] handle dangling references when firewall objects go away Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 01/16] helpers: add helpers to update firewall object references Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 02/16] parser: do not log errors for disabled rules Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 03/16] api: ipset: add option to update references on edit Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 04/16] api: ipset: add option to handle dangling references on delete Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 05/16] api: aliases: add option to update references on edit Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-firewall v3 06/16] api: aliases: add option to handle dangling references on delete Arthur Bied-Charreton
2026-09-25 9:42 ` SPAM: [PATCH pve-firewall v3 07/16] firewall: tests: add tests for object reference update logic Arthur Bied-Charreton
2026-09-25 9:42 ` SPAM: [PATCH pve-network v3 08/16] apply: add option to handle dangling references on VNet deletion Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH qemu-server v3 09/16] api: destroy_vm: add option to handle dangling IPSet references Arthur Bied-Charreton
2026-09-25 9:42 ` SPAM: [PATCH pve-container v3 10/16] " Arthur Bied-Charreton
2026-09-25 9:42 ` SPAM: [PATCH pve-manager v3 11/16] ui: firewall: add common widgets for deleting and updating references Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-manager v3 12/16] ui: firewall: ipset: add controls to update/delete references on edit Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-manager v3 13/16] ui: firewall: aliases: " Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-manager v3 14/16] ui: sdn: apply: add control for dangling IPSet references Arthur Bied-Charreton
2026-09-25 9:42 ` [PATCH pve-manager v3 15/16] ui: guest destroy: use let for non-constant variable bindings Arthur Bied-Charreton
2026-09-25 9:42 ` Arthur Bied-Charreton [this message]
2026-09-25 11:05 ` SPAM: [PATCH container/firewall/manager/network/qemu-server v3 00/16] handle dangling references when firewall objects go away Arthur Bied-Charreton
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=20260925094230.844917-17-a.bied-charreton@proxmox.com \
--to=a.bied-charreton@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 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.