From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-manager v3 14/16] ui: sdn: apply: add control for dangling IPSet references
Date: Fri, 25 Sep 2026 11:42:28 +0200 [thread overview]
Message-ID: <20260925094230.844917-15-a.bied-charreton@proxmox.com> (raw)
In-Reply-To: <20260925094230.844917-1-a.bied-charreton@proxmox.com>
Applying an SDN configuration that removes a VNet also removes the
four IPSets auto-generated for it [0], so rules referencing those no
longer resolve and are dropped from the generated ruleset.
Replace the plain confirmation message box with a window carrying the
shared selector, so those rules can be disabled or deleted in the same
step. The Apply button first queries the pending VNets, and the window
only shows the selector if the apply actually removes one, since there
is nothing to decide otherwise.
[0] https://pve.proxmox.com/wiki/Software-Defined_Network#pvesdn_firewall_integration
Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
www/manager6/sdn/StatusView.js | 105 ++++++++++++++++++++++++++-------
1 file changed, 85 insertions(+), 20 deletions(-)
diff --git a/www/manager6/sdn/StatusView.js b/www/manager6/sdn/StatusView.js
index fada5041..79ca815c 100644
--- a/www/manager6/sdn/StatusView.js
+++ b/www/manager6/sdn/StatusView.js
@@ -1,3 +1,74 @@
+Ext.define('PVE.sdn.ApplyWindow', {
+ extend: 'Proxmox.window.Edit',
+ alias: 'widget.pveSdnApplyWindow',
+
+ title: gettext('Apply SDN Configuration'),
+
+ url: '/cluster/sdn',
+ method: 'PUT',
+ isCreate: true,
+ submitText: gettext('Apply'),
+ width: 600,
+
+ // IDs of the VNets that this apply removes, empty if it removes none
+ removedVnets: [],
+
+ initComponent: function () {
+ let me = this;
+
+ me.items = [
+ {
+ xtype: 'displayfield',
+ value: gettext(
+ 'Applying pending SDN changes will also apply any pending local node network changes.',
+ ),
+ },
+ ];
+
+ // the auto-generated IPSets of a removed VNet go away with it, so only then is there
+ // anything to decide about the rules referencing them
+ if (me.removedVnets.length !== 0) {
+ let removedHint = Ext.htmlEncode(
+ Ext.String.format(
+ gettext('This removes the following VNet(s): {0}.'),
+ me.removedVnets.join(', '),
+ ),
+ );
+ let helpLink = Ext.htmlEncode(
+ Proxmox.Utils.get_help_link('pvesdn_firewall_integration'),
+ );
+ let helpLabel = Ext.htmlEncode(gettext('their auto-generated IPSets'));
+ let refsHint = Ext.String.format(
+ gettext('Firewall rules referencing {0} will no longer resolve.'),
+ `<a target="_blank" href="${helpLink}">${helpLabel}</a>`,
+ );
+
+ me.items.push(
+ {
+ xtype: 'displayfield',
+ userCls: 'pmx-hint',
+ value: `${removedHint}<br>${refsHint}`,
+ },
+ {
+ xtype: 'pveFirewallDanglingReferences',
+ name: 'dangling-ipset-references',
+ value: 'keep',
+ labelWidth: 200,
+ keepTip: gettext(
+ 'Keep referencing rules. They are dropped from the generated ruleset and shown as invalid until the VNet is recreated.',
+ ),
+ disableTip: gettext(
+ 'Disable referencing rules, keeping them in the firewall configuration.',
+ ),
+ dropTip: gettext('Delete referencing rules.'),
+ },
+ );
+ }
+
+ me.callParent();
+ },
+});
+
Ext.define(
'PVE.sdn.StatusView',
{
@@ -45,26 +116,20 @@ Ext.define(
{
text: gettext('Apply'),
handler: function () {
- Ext.Msg.show({
- title: gettext('Confirm'),
- icon: Ext.Msg.QUESTION,
- msg: gettext(
- 'Applying pending SDN changes will also apply any pending local node network changes. Proceed?',
- ),
- buttons: Ext.Msg.YESNO,
- callback: function (btn) {
- if (btn === 'yes') {
- Proxmox.Utils.API2Request({
- url: '/cluster/sdn/',
- method: 'PUT',
- waitMsgTarget: me,
- failure: (response) =>
- Ext.Msg.alert(
- gettext('Error'),
- response.htmlStatus,
- ),
- });
- }
+ Proxmox.Utils.API2Request({
+ url: '/cluster/sdn/vnets',
+ method: 'GET',
+ params: { pending: 1 },
+ waitMsgTarget: me,
+ failure: (response) =>
+ Ext.Msg.alert(gettext('Error'), response.htmlStatus),
+ success: function (response) {
+ Ext.create('PVE.sdn.ApplyWindow', {
+ removedVnets: response.result.data
+ .filter((vnet) => vnet.state === 'deleted')
+ .map((vnet) => vnet.vnet),
+ autoShow: true,
+ });
},
});
},
--
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 ` Arthur Bied-Charreton [this message]
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 ` [PATCH pve-manager v3 16/16] ui: guest destroy: add control for dangling IPSet references Arthur Bied-Charreton
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-15-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.