[Bug 1614061] Re: "netplan apply": don't restart networkd/NM synchronously

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.8

---------------
nplan (0.8) yakkety; urgency=medium

  * tests/cli.py: Test "generate" more precisely
  * Let "make coverage" fail if coverage is < 100%
  * Support /run/netplan/*.yaml files.
    This is useful if you want to try out a new network config before "committing"
    it to /etc: if your remote server is still reachable after "apply", you copy
    the files to /etc; otherwise rebooting will go back to the known-good state.
  * If global renderer is set to NM, allow NM to manage all devices.
    By default, NetworkManager only manages wifi and wwan devices (via
    /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf). If global
    renderer is set to NetworkManager, disable that file in /run so that NM will
    once again manage all devices.
    This should be configured on desktop systems.
  * netplan apply: Asynchronously restart networkd/NM.
    This avoids deadlocks when calling "apply" during the boot sequence.
    (LP: #1614061)

 -- Martin Pitt <martin.pitt at ubuntu.com>  Wed, 17 Aug 2016 16:03:33
+0200

** Changed in: nplan (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nplan in Ubuntu.
https://bugs.launchpad.net/bugs/1614061

Title:
  "netplan apply": don't restart networkd/NM synchronously

Status in nplan package in Ubuntu:
  Fix Released

Bug description:
  It might happen that someone tries to run "netplan apply" from within
  the initial boot transaction, in some kind of "firstboot.service"
  setup utility. Running systemctl restart networkd there would
  deadlock, so let's rather do this with --no-block.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1614061/+subscriptions