From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH ifupdown2 1/1] d/patches: fix issue when reloading bonds with altname slaves
Date: Wed, 30 Jul 2025 19:30:50 +0200 [thread overview]
Message-ID: <175389664802.3834260.2665932750106341945.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250730163910.412108-1-s.hanreich@proxmox.com>
On Wed, 30 Jul 2025 18:39:08 +0200, Stefan Hanreich wrote:
> When reloading the network configuration via ifupdown2 and a bond has
> bridge-slaves defined with their altname, the bond would break after
> reloading - then work again after every second reload.
>
> The issue for this is that the port list is parsed directly via
> parse_port_list, provided by the modulebase. This method doesn't do
> any translation of altnames. This leads to a wrong detection of
> pre-existing slave interfaces when reloading. ifupdown then tries to
> enslave the interfaces with the 'real' name and un-enslave the
> interfaces with the altname, leading to no interfaces being enslaved
> to the bond at all.
>
> [...]
Applied, thanks!
[1/1] d/patches: fix issue when reloading bonds with altname slaves
commit: 6ccaf70388e56d37dfafdba9f50163210f808f57
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-30 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:39 [pve-devel] " Stefan Hanreich
2025-07-30 17:29 ` Thomas Lamprecht
2025-07-30 17:30 ` Thomas Lamprecht [this message]
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=175389664802.3834260.2665932750106341945.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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.