automatically start networkd if YAML config is present

Bug #1607693 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nplan (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

networkd is not enabled by default as it would be a pointlessly running daemon unless there is some actual configuration. netplan should automatically start networkd on boot if /etc/netplan/*.yaml exists so that it does not need to be enabled explicitly.

Martin Pitt (pitti)
Changed in nplan (Ubuntu):
status: New → Triaged
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → High
Revision history for this message
Martin Pitt (pitti) wrote :

Plan:
 - Move "generate" from being a .service to a systemd system-generator. Create a flag file in /run to only run at boot, not every time on daemon-reload.
 - The future "netplan apply" will remove the flag file and re-run the generator.
 - To provide easier access to YAML errors, provide a "netplan check" verb.

Martin Pitt (pitti)
Changed in nplan (Ubuntu):
status: Triaged → In Progress
milestone: none → ubuntu-16.08
Martin Pitt (pitti)
Changed in nplan (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nplan - 0.5

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

  * Recognize booean values as per YAML spec (LP: #1606839)
  * Add explicit systemd test dependency
  * networkd: Disable LinkLocalAddressing and RA for bridge components
  * Move "generate" from a systemd unit to a systemd generator
  * Automatically start networkd iff there is any networkd configuration
    (LP: #1607693)

 -- Martin Pitt <email address hidden> Mon, 01 Aug 2016 17:27:54 +0200

Changed in nplan (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.