Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.
The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require rebooting
rather than just running 'netplan apply').
Reassigning to systemd for investigation, we do have unit / autopkg
tests running for netplan which look like 802.3ad is correctly set, but
they do not interact with other network devices (there are no other
network devices in the test environment).
Furthermore, is anything beyond the physical network adapters configured
to used 802.3ad? This is important for the bonding to work.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1753431
Title:
bonding does not works
Status in systemd package in Ubuntu:
Incomplete
Bug description:
I'm working on libvirt/kvm hypervisor
I user 2 bondind interfaces:
eno1 + eno2 => bond0 via "netplan" ("service" interface for hypervisor)
eno3 + eno4 => bond1 via "ifupdown" ("virtualization" interface for libvirt)
Since last upgrade (today), i got "Warning, no 802.3ad response from
the link partner ..." with dmesg, bonding doesn't longer works with
"netplan" and "ifupdown".
Kernel problem ? ifenslave problem ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
