Network configuration doesn't survive reboots after bionic dist-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ifupdown (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/
About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up.
To recover the machine, what i did is:
1. From the console, brought up the interfaces manually (eno1)
2. added an IP address manually (ip addr add)
3. Configured netplan and applied the config:
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: no
dhcp6: no
usb0:
dhcp4: no
bridges:
br0:
dhcp4: no
5. Interfaces dont get configured correctly:
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
17: eno1: <BROADCAST,
link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.13/24 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::eea8:
valid_lft forever preferred_lft forever
19: usb0: <BROADCAST,
link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff
inet6 fe80::20e:
valid_lft forever preferred_lft forever
22: wlp2s0: <BROADCAST,
link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff
6. on reboot, the machine goes back to have no networking again, at all.
Note that I also have /e/n/i configured.
I dont believe this is a cloud-init issue provided that cloud-init seems to not run networking on reboots, and networking is disabled:
ubuntu@ maas00: /etc/cloud/ cloud.cfg. d$ cat curtin- disable- cloudinit- networking. cfg
network: {config: disabled}