From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-manager v5 23/27] ui: sdn: apply: add control for dangling IPSet references
Date: Tue, 3 Nov 2026 09:43:24 +0100 [thread overview]
Message-ID: <20261103084328.203492-24-a.bied-charreton@proxmox.com> (raw)
In-Reply-To: <20261103084328.203492-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 | 118 +++++++++++++++++++++++++++------
1 file changed, 98 insertions(+), 20 deletions(-)
diff --git a/www/manager6/sdn/StatusView.js b/www/manager6/sdn/StatusView.js
index fada5041..ce919639 100644
--- a/www/manager6/sdn/StatusView.js
+++ b/www/manager6/sdn/StatusView.js
@@ -1,3 +1,87 @@
+// scanned by asciidoc-pve, so the anchor lands in the documentation index
+const VNET_IPSETS_HELP = {
+ onlineHelp: 'pve_firewall_automatically_generated_ipsets',
+};
+
+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,
+
+ 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.',
+ ),
+ },
+ ];
+
+ 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(VNET_IPSETS_HELP.onlineHelp));
+ 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: 'pveFirewallReferenceAction',
+ name: 'dangling-ipset-references',
+ preferredValue: 'drop',
+ fieldLabel: gettext('Referencing rules'),
+ labelWidth: 200,
+ referenceActions: [
+ {
+ text: gettext('Keep'),
+ value: 'keep',
+ description: gettext(
+ "Do not touch firewall rules referencing this VNet's IPSets.",
+ ),
+ },
+ {
+ text: gettext('Disable'),
+ value: 'disable',
+ description: gettext("Disable firewall rules referencing this VNet's IPSets."),
+ },
+ {
+ text: gettext('Delete'),
+ value: 'drop',
+ description: gettext("Delete firewall rules referencing this VNet's IPSets."),
+ },
+ ],
+ },
+ );
+ }
+
+ me.callParent();
+ },
+});
+
Ext.define(
'PVE.sdn.StatusView',
{
@@ -45,26 +129,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-11-03 8:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:43 [PATCH container/docs/firewall/manager/network/qemu-server v5 00/27] handle dangling references when firewall objects go away Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 01/27] firewall: move object reference helpers to their own module Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 02/27] firewall: references: add helpers to update object references Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 03/27] firewall: references: log the references an object update touched Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 04/27] firewall: references: add wrappers for the SDN-generated IPSets Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 05/27] firewall: parser: do not log errors for disabled rules Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 06/27] firewall: ipset: add option to handle dangling references on rename Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 07/27] firewall: ipset: add option to handle dangling references on delete Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 08/27] firewall: aliases: add option to handle dangling references on rename Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 09/27] firewall: aliases: add option to handle dangling references on delete Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 10/27] firewall: api: run reference updates as tasks Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 11/27] firewall: tests: add tests for object reference updates Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 12/27] firewall: references: handle security groups Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 13/27] firewall: groups: add option to handle dangling references on rename Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-firewall v5 14/27] fix #8176: firewall: groups: handle dangling references on delete Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-network v5 15/27] apply: add option to handle dangling references on VNet deletion Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH qemu-server v5 16/27] api: destroy_vm: add option to handle dangling IPSet references Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-container v5 17/27] " Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-docs v5 18/27] firewall: remove trailing spaces Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-docs v5 19/27] firewall: document renaming and removing objects Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 20/27] ui: firewall: add a common widget for handling dangling references Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 21/27] ui: firewall: ipset: add controls for " Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 22/27] ui: firewall: aliases: " Arthur Bied-Charreton
2026-11-03 8:43 ` Arthur Bied-Charreton [this message]
2026-11-03 8:43 ` [PATCH pve-manager v5 24/27] ui: guest destroy: use let for non-constant variable bindings Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 25/27] ui: guest destroy: add control for dangling IPSet references Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 26/27] ui: firewall: show the task for reference updates Arthur Bied-Charreton
2026-11-03 8:43 ` [PATCH pve-manager v5 27/27] ui: firewall: groups: add controls for dangling references 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=20261103084328.203492-24-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox