YAML configs wiped out from /run/netplan

[Mathieu Trudel-Lapierre]

[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'.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

This bug was fixed in the package netplan.io - 0.35

---------------
netplan.io (0.35) bionic; urgency=medium

  * debian/postinst: fix version check for when to write breadcrumbs.
    (LP: #1756742)
  * bonds/bridges: Support specifying time-based values with "ms" suffix when
    the value should be in milliseconds; while keeping support for the previous
    behavior of handling values are pure seconds when no suffix is present.
    (LP: #1745597)
  * IPv6: accept-ra should default to being unset, so that the kernel default
    can be used. (LP: #1732002)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
    with Windows Server-based DHCP servers which don't support RFC 4361.
    (LP: #1738998)
  * docs, examples: reformat comments in examples, add standalone example files
  * debian/docs, debian/netplan.io.install: install doc and examples in the
    right locations.
  * netplan try: allow users to preview/test and approve network configuration
    changes, and automatically revert if they are not accepted. (LP: #1764824)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
    YAML configurations in that directory, we just need to remove generated
    wpasupplicant configs. (LP: #1764869)
  * debian/control: add bash-completion to Build-Depends to make sure we do
    install completion files in the right location.

 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 17 Apr 2018 21:49:21 -0400

[Brian Murray (brian-murray)]

Hello Mathieu, or anyone else affected,

Accepted nplan into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Brian Murray (brian-murray)]

Hello Mathieu, or anyone else affected,

Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Mathieu Trudel-Lapierre (cyphermox)]

Verification-done for artful: nplan 0.32~17.10.4
Verification-done for xenial: nplan 0.32~16.04.5

Verified that a random file "/run/netplan/toto.yaml" present on the system is removed when running "netplan apply" with the previous version of nplan, and remains in place when the new version is installed: additionally, wpa-* files are removed as they should by the process.

ubuntu@heroic-ibex:~$ sudo mkdir /run/netplan
ubuntu@heroic-ibex:~$ sudo touch /run/netplan/wpa-toto.conf
ubuntu@heroic-ibex:~$ sudo touch /run/netplan/someotherfile
ubuntu@heroic-ibex:~$ sudo touch /run/netplan/toto.yaml
ubuntu@heroic-ibex:~$ ls -l /run/netplan
total 0
-rw-r--r-- 1 root root 0 May 15 15:22 someotherfile
-rw-r--r-- 1 root root 0 May 15 15:22 toto.yaml
-rw-r--r-- 1 root root 0 May 15 15:21 wpa-toto.conf
ubuntu@heroic-ibex:~$ sudo netplan apply
ubuntu@heroic-ibex:~$ ls -l /run/netplan
total 0
-rw-r--r-- 1 root root 0 May 15 15:22 someotherfile
-rw-r--r-- 1 root root 0 May 15 15:22 toto.yaml
ubuntu@heroic-ibex:~$

[Launchpad Janitor (janitor)]

This bug was fixed in the package nplan - 0.32~17.10.4

---------------
nplan (0.32~17.10.4) artful; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
    "mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
    denote the migration to using netplan. (LP: #1756742)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
    with Windows Server-based DHCP servers which don't support RFC 4361.
    (LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
    can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
    and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
    connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
    YAML configurations in that directory, we just need to remove generated
    wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 08 May 2018 11:04:30 -0400

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package nplan - 0.32~16.04.5

---------------
nplan (0.32~16.04.5) xenial; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
    "mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * Do not attempt to rebind driver 'qeth'. (LP: #1756322)
  * Allow setting ClientIdentifier=mac for networkd-renderered devices
    (LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
    can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
    and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
    connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
    YAML configurations in that directory, we just need to remove generated
    wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 08 May 2018 10:36:24 -0400