[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.96-0ubuntu2

---------------
netplan.io (0.96-0ubuntu2) disco; urgency=medium

  * d/p/0001-Automatically-skip-tests-when-wifi-is-clearly-unavai.patch:
    Update wifi tests to try to make them more reliable.
  * debian/tests/control: explicilty mark wifi tests flaky.

 -- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com>  Thu, 14 Mar 2019
14:11:47 -0400

** Changed in: netplan.io (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1811868

Title:
  networkd/NetworkManager are not re-started on netplan apply when
  config files are removed

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released

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:
                  macaddress: 78:45:c4:ef:b6:39
              mtu: 1500
              set-name: eno1
          eno2:
              match:
                  macaddress: 78:45:c4:ef:b6:3b
              mtu: 1500
              set-name: eno2
          eno3:
              match:
                  macaddress: 78:45:c4:ef:b6:3d
              mtu: 1500
              set-name: eno3
          eno4:
              match:
                  macaddress: 78:45:c4:ef:b6:3f
              mtu: 1500
              set-name: eno4
          enp4s0f0:
              match:
                  macaddress: 00:0a:f7:72:a7:28
              mtu: 9000
              set-name: enp4s0f0
          enp4s0f1:
              match:
                  macaddress: 00:0a:f7:72:a7:2a
              mtu: 9000
              set-name: enp4s0f1
          enp5s0f0:
              match:
                  macaddress: 00:0e:1e:ac:67:00
              mtu: 9000
              set-name: enp5s0f0
          enp5s0f1:
              match:
                  macaddress: 00:0e:1e:ac:67:02
              mtu: 9000
              set-name: enp5s0f1
      bonds:
          bond0:
              interfaces:
              - enp4s0f0
              - enp5s0f0
              macaddress: 52:54:45:7f:7b:6f
              mtu: 9000
              parameters:
                  down-delay: 0
                  lacp-rate: fast
                  mii-monitor-interval: 100
                  mode: 802.3ad
                  transmit-hash-policy: layer3+4
                  up-delay: 0
          bond1:
              interfaces:
              - enp4s0f1
              - enp5s0f1
              macaddress: 52:54:45:26:cb:7b
              mtu: 9000
              parameters:
                  down-delay: 0
                  lacp-rate: fast
                  mii-monitor-interval: 100
                  mode: 802.3ad
                  transmit-hash-policy: layer3+4
                  up-delay: 0
          bondm:
              addresses:
              - 10.20.0.84/24
              gateway4: 10.20.0.1
              interfaces:
              - eno1
              - eno2
              - eno3
              - eno4
              macaddress: 52:54:45:7e:d0:7f
              mtu: 1500
              nameservers:
                  addresses:
                  - 10.20.0.14
                  - 10.20.0.10
                  - 10.20.0.11
                  - 10.20.0.12
                  search:
                  - maas
              parameters:
                  down-delay: 0
                  lacp-rate: fast
                  mii-monitor-interval: 100
                  mode: 802.3ad
                  transmit-hash-policy: layer3+4
                  up-delay: 0
      vlans:
          bond0.804:
              addresses:
              - 10.20.16.50/24
              id: 804
              link: bond0
              mtu: 1500
              nameservers: &id001
                  addresses:
                  - 10.20.0.14
                  - 10.20.0.10
                  - 10.20.0.11
                  - 10.20.0.12
                  search:
                  - maas
          bond0.805:
              addresses:
              - 10.20.20.50/24
              id: 805
              link: bond0
              mtu: 1500
              nameservers: *id001
          bond0.807:
              addresses:
              - 10.20.28.2/24
              id: 807
              link: bond0
              mtu: 9000
              nameservers: *id001
          bond0.808:
              addresses:
              - 10.20.32.50/24
              id: 808
              link: bond0
              mtu: 9000
              nameservers: *id001
          bond0.810:
              addresses:
              - 10.20.33.2/29
              id: 810
              link: bond0
              mtu: 1500
              nameservers: *id001

  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/NetworkManager are re-started on
  "netplan apply" when there are files created by netplan in the
  corresponding /run/* folder.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions