YAML configs wiped out from /run/netplan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned | ||
nplan (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Netboot users, and any scenario where YAML configuration is written to /run/netplan.
[Test case]
1) Run 'sudo netplan apply'
2) Verify that existing configuration *.yaml files in /run/netplan is not removed.
[Regression Potential]
/run/netplan is meant as a location for yaml configuration generated by other parts of the system, or by the boot processes, to be used and complement / override local config in /etc/netplan. Additional files are created in /run/netplan (such as wpa configuration when using wifi) which must be removed. Removal of the netplan configuration files may lead to incomplete configuration for network devices. This may cause a system to lose connectivity. Changes in network connectivity following "netplan apply" where configuration didn't otherwise change in /etc/netplan/*.yaml may indicate a regression.
---
Any .yaml file in /run/netplan are wiped out when 'netplan generate' is run. This is wrong, we might actually want to have .yaml files there for netplan configuration.
What we don't want, however, is for generated wpa-*.conf files to be left around: wpasupplicant configuration really does need to go, as it will be generated again by 'netplan generate'.
Changed in nplan (Ubuntu): | |
status: | New → In Progress |
description: | updated |
Changed in nplan (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in netplan.io (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in netplan.io (Ubuntu Artful): | |
status: | New → Invalid |
Status changed to 'Confirmed' because the bug affects multiple users.