Public bug reported:
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
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: bond kernel-bug netplan network
** Summary changed:
- Default bonded network fails after kernel update.
+ System generated network bond fails after kernel update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909792
Title:
System generated network bond fails after kernel update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1909792/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
