From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/3] network interface pinning fixes
Date: Fri, 18 Jul 2025 14:33:10 +0200 [thread overview]
Message-ID: <20250718123313.208460-1-s.hanreich@proxmox.com> (raw)
Provides the following fixes:
* check for changes in the SDN configuration and only runs pve-sdn-commit if
there are changes to the SDN configuration
* pve-{sdn, firewall}-commit now wait for quorum on startup
* adds a missing undef check in the update controllers logic of the pinning tool
pve-manager:
Stefan Hanreich (3):
network-interface-pinning: avoid comparing undefined string
{sdn, firewall}-commit: wait for quorum
sdn-commit: only reload ifupdown if sdn configuration changed
PVE/CLI/proxmox_network_interface_pinning.pm | 2 +-
bin/pve-firewall-commit | 10 +++
bin/pve-sdn-commit | 75 ++++++++++++++++++++
services/pve-firewall-commit.service | 2 +-
services/pve-sdn-commit.service | 2 +-
5 files changed, 88 insertions(+), 3 deletions(-)
Summary over all repositories:
5 files changed, 88 insertions(+), 3 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-07-18 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 12:33 Stefan Hanreich [this message]
2025-07-18 12:33 ` [pve-devel] [PATCH pve-manager 1/3] network-interface-pinning: avoid comparing undefined string Stefan Hanreich
2025-07-18 12:33 ` [pve-devel] [PATCH pve-manager 2/3] {sdn, firewall}-commit: wait for quorum Stefan Hanreich
2025-07-18 12:33 ` [pve-devel] [PATCH pve-manager 3/3] sdn-commit: only reload ifupdown if sdn configuration changed Stefan Hanreich
2025-07-18 12:45 ` [pve-devel] applied: [PATCH manager 0/3] network interface pinning fixes Thomas Lamprecht
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=20250718123313.208460-1-s.hanreich@proxmox.com \
--to=s.hanreich@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.