Netplan crashes when attempting to rename interface in 'up' state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
Critical
|
Heitor Alves de Siqueira | ||
netplan.io (Ubuntu) |
Fix Released
|
Critical
|
Heitor Alves de Siqueira | ||
Bionic |
Fix Released
|
Critical
|
Heitor Alves de Siqueira | ||
Eoan |
Fix Released
|
Critical
|
Heitor Alves de Siqueira | ||
Focal |
Fix Released
|
Critical
|
Heitor Alves de Siqueira | ||
Groovy |
Fix Released
|
Critical
|
Heitor Alves de Siqueira |
Bug Description
[Impact]
Netplan crashes when trying to apply rules to certain interfaces
[Description]
Starting with version 0.99, netplan introduced a different way of processing link changes that introduced a regression handling interfaces that are still in the 'up' state.
It's possible for interfaces to be marked for link operations (e.g. "set-name") by their MAC address, even if the interface should have been skipped due to being up.
This regression has been fixed upstream by the commit below:
- Fix process_
The fix is not currently present in any Ubuntu release, and the following Netplan 0.99 versions are affected:
$ rmadison netplan.io -s bionic-
netplan.io | 0.99-0ubuntu3~
netplan.io | 0.99-0ubuntu3~
netplan.io | 0.99-0ubuntu3~
netplan.io | 0.99-0ubuntu3 | groovy | source, ...
[Test Case]
1) Create new dummy interface for testing
# modprobe dummy
# ip link add eth0-test type dummy
# ip link set eth0-test up
2) Add netplan file for new interface with "set-name" directive
# cat /etc/netplan/
network:
version: 2
ethernets:
eth0-test:
match:
macaddress: 56:f6:56:31:2f:ae
set-name: uplink
3) Attempt to apply changes
# netplan apply
Traceback (most recent call last):
File "/usr/sbin/
netplan.main()
File "/usr/share/
self.
File "/usr/share/
self.func()
File "/usr/share/
self.
File "/usr/share/
self.func()
File "/usr/share/
stderr=
File "/usr/lib/
raise CalledProcessEr
subprocess.
[Regression Potential]
The upstream patch restores the behavior present in 0.98 versions, so the regression potential should be low.
Possible issues with this fix could cause netplan to skip interfaces it's not meant to, but the netplan test suite and general smoke testing revealed no major problems.
tags: | added: sts |
Changed in netplan: | |
status: | Fix Committed → Fix Released |
This has also appeared in the maas images from the daily sync, and we are no longer able to commission nodes correctly
This is effecting a customer, after they were deploying new nodes into the PCB build
I have reproduced this problem internally, and can say that it's due to an updated netplan.io package from 0.98 to 0.99
From the daily sync of image on 7th May everything works, latest image from 22nd May doesn't. The following pastebin a transcript of a node booted from the 7th May image, and showing netplan working, and then upgrading netplan.io then causes the machine not to apply the netplan configuration
https:/ /pastebin. ubuntu. com/p/6bFSns6WG V/