"netplan apply": don't restart networkd/NM synchronously
Bug #1614061 reported by
Martin Pitt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nplan (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
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.
| Changed in nplan (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Martin Pitt (pitti) |
| milestone: | none → ubuntu-16.08 |
| Changed in nplan (Ubuntu): | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in nplan (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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/
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 <email address hidden> Wed, 17 Aug 2016 16:03:33 +0200