We've seen a similar-sounding issue in the past, but couldn't get it tracked down to the root cause.
Is it possible to enable some instrumentation in the /etc/network/interfaces and obtain some data on a failing occurrence? What we've used in the past is adding something like pre-up echo 'file bond_3ad.c +p' > /sys/kernel/debug/dynamic_debug/control pre-up echo 'file bond_main.c +p' > /sys/kernel/debug/dynamic_debug/control to the /e/n/i section for the bond itself, and post-up tcpdump -U -p -w /tmp/eth4.td -i eth4 ether proto 0x8809 & to the sections for each slave in the bond (adjusting the "eth4" above to the actual interface name). The bond debug will appear in the kernel log, and the tcpdump data will have to copied from the output file specified on the tcpdump command line (and the tcpdump process terminated if need be). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
