Okay, I have attempted to backport this patch to Jammy today. However, the upstream commit mentioned depends on another commit[1]. Unfortunately, I previously looked into backporting that commit in bug 2003250, but as I describe in the bug, it does not behave correctly when backported to Jammy. The same issue came up today when I tested all of these patches together. In particular, the bond is never fully configured on boot, and the subordinate device is never fully re- configured after `networkctl reconfigure`.
I do not have the time to investigate the root cause and write a proper backport for these patches, so this will not be prioritized for 22.04. Sorry :/ [1] https://github.com/systemd/systemd/pull/25162/commits/ebf95ef2fa915a7f0e2e747651391f07aa2fb180 ** Tags removed: systemd-sru-next ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Assignee: Nick Rosbrook (enr0n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052137 Title: bonded link goes down on reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2052137/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
