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 <cypher...@ubuntu.com> Tue, 08 May 2018
11:04:30 -0400
** Changed in: nplan (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764869
Title:
YAML configs wiped out from /run/netplan
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in netplan.io source package in Xenial:
Invalid
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Artful:
Invalid
Status in nplan source package in Artful:
Fix Released
Bug description:
[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'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1764869/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
