System generated network bond fails after kernel update.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan.io (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Server info (20.04)
After i updated my docker server yesterday i had to reboot because of a kernel update (new version 5.4.0-58-generic x86_64). My main network interface that i use all of a sudden failed to apply its configuration and was not able to connect. I believe this issue is linked to this bug (Bug #1860926) but not exactly the same issue.
When setting up my server on first install i used the startup walk-through to auto configure my eno1&eno2 network bond. I unfortunately didn't save the previous netplan yaml to post here,but it had said it was written by subiquity. Every time i tried to apply the netplan it replied that eno2 was not defined. I had to change the yaml to this configuration to get my link back up.
network:
bonds:
bond0:
interfaces:
- eno1
- eno2
parameters:
mode: balance-rr
ethernets:
eno1: {}
eno2: {}
version: 2
bridges:
br0:
addresses:
- 172.16.10.2/24
dhcp4: false
gateway4: 172.16.10.254
nameservers:
addresses:
- 172.16.10.251
- 172.16.10.254
search: []
interfaces:
- bond0
I found this in my syslog right after the reboot from update,
/usr/lib/
PRIORITY 3
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
SYSLOG_PID 675
_BOOT_ID de464fb514a34d1
_HOSTNAME bagul.dev
_MACHINE_ID e610a37f963a4ad
_SOURCE_
_TRANSPORT kernel
__CURSOR s=0b1205c7c02b4
__MONOTONIC_
__REALTIME_
summary: |
- Default bonded network fails after kernel update. + System generated network bond fails after kernel update. |
description: | updated |
affects: | ubuntu → netplan.io (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1909792/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]