networkd/NetworkManager are not re-started on netplan apply when config files are removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan |
Fix Released
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
All users of netplan when changing configuration and removing devices.
[Test case]
1) Set up a configuration with additiona devices:
network:
version: 2
ethernets:
eno1:
match:
mtu: 1500
eno2:
match:
mtu: 1500
eno3:
match:
mtu: 1500
eno4:
match:
mtu: 1500
enp4s0f0:
match:
mtu: 9000
enp4s0f1:
match:
mtu: 9000
enp5s0f0:
match:
mtu: 9000
enp5s0f1:
match:
mtu: 9000
bonds:
bond0:
- enp4s0f0
- enp5s0f0
mtu: 9000
bond1:
- enp4s0f1
- enp5s0f1
mtu: 9000
bondm:
- 10.20.0.84/24
- eno1
- eno2
- eno3
- eno4
mtu: 1500
- 10.20.0.14
- 10.20.0.10
- 10.20.0.11
- 10.20.0.12
- maas
vlans:
bond0.804:
- 10.20.16.50/24
id: 804
link: bond0
mtu: 1500
- 10.20.0.14
- 10.20.0.10
- 10.20.0.11
- 10.20.0.12
- maas
bond0.805:
- 10.20.20.50/24
id: 805
link: bond0
mtu: 1500
bond0.807:
- 10.20.28.2/24
id: 807
link: bond0
mtu: 9000
bond0.808:
- 10.20.32.50/24
id: 808
link: bond0
mtu: 9000
bond0.810:
- 10.20.33.2/29
id: 810
link: bond0
mtu: 1500
2) Run 'netplan apply' to configure the devices.
3) Verify bond0, bond1, bondm devices are created.
4) Configure netplan again:
network:
version: 2
renderer: NetworkManager
5) Run 'netplan apply'
6) Verify that the daemons are restarted, and devices are deconfigured (this may not mean the devices are removed).
[Regression potential]
Pay attention to issues with network connectivity caused by the restarting of daemons, or any other issues that could potentially be caused by the fact that the backend daemons are being restarted when configurations have been removed.
---
The network managers networkd/
However, if we change from a configuration in which we have config files in /run to one where we remove those files, the services are not re-started. For instance, if we switch from a configuration in which some devices are managed by networkd to one in which all devices are managed by NM, networkd is not re-started, so it still thinks it should manage those devices.
Changed in netplan: | |
status: | New → Fix Released |
description: | updated |
MP with fix: https:/ /github. com/CanonicalLt d/netplan/ pull/68