This bug was fixed in the package nplan - 0.23~16.10.1
---------------
nplan (0.23~16.10.1) yakkety; urgency=medium
* Backport netplan 0.23 to 16.10. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful; urgency=medium
* Add support for setting a custom MAC address on all device types.
(LP: #1690388)
* Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
changes.
nplan (0.21) artful; urgency=medium
[ Ryan Harper ]
* Add support for setting MTU on a device. (LP: #1668693)
[ Mathieu Trudel-Lapierre ]
* Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
* debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
Both ship the same /usr/sbin/netplan. (LP: #1665842)
nplan (0.20) zesty; urgency=medium
* tests/integration.py: increase timeout for integration tests (networkd and
NetworkManager "wait-online" checks) to account for longer bring-up times
when dealing with stacked virtual devices.
nplan (0.19) zesty; urgency=medium
* Add support for unordered definition of network devices: you can now
specify a virtual devices before their member devices. (LP: #1670495)
* Allow setting up the STP state for a bridge. (LP: #1665088)
* Document bond/bridge parameters support. (LP: #1664702)
nplan (0.18) zesty; urgency=medium
* debian/tests/integration.py: in some cases 'iw reg get' may qualify the
reg domain results with 'global'; we must not let that trip up tests when
they are run on Ubuntu infrastructure vs. local tests.
nplan (0.17) zesty; urgency=medium
* New release:
- Add support for configuring bonds.
- Add support for configuring bridges.
nplan (0.16) zesty; urgency=medium
[ Martin Pitt ]
* doc/example-config: Adjust "routes:" example.
It does not make sense to make "routes:" a global thing, they should be
tied to an interface so that the route is only set when the corresponding
interface exists and is up, and the config is not split in two parts.
* doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)
[ Mathieu Trudel-Lapierre ]
* Fix coverage for src/netplan to be 100%, and fail if coverage falls below
that mark again.
* Add support for specifying routes.
nplan (0.15) zesty; urgency=medium
* tests/generate.py: Fix PEP-8 error (newly detected by -proposed
pycodestyle).
nplan (0.14) zesty; urgency=medium
* tests/generate.py: Introduce macros for commonly expected networkd output
* networkd: Use NetworkManager compatible DHCP route metrics (LP: #1639754)
* doc/netplan.md: Fix wrong wifi reference in "br0" example
* doc/netplan.md: Clarify introduction
* tests/integration.py: Fix race condition with waiting for networkd
nplan (0.13) zesty; urgency=medium
[ Jonathan Cave ]
* Blacklist mwifiex_pcie from rebinds (work around LP: #1630285)
[ Martin Pitt ]
* Add support for nameservers (LP: #1626617)
-- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Tue, 06 Jun 2017
17:25:57 -0700
** Changed in: nplan (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** Changed in: nplan (Ubuntu Zesty)
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/1688632
Title:
nplan 0.23 update
Status in nplan package in Ubuntu:
Fix Released
Status in nplan source package in Xenial:
Fix Released
Status in nplan source package in Yakkety:
Fix Released
Status in nplan source package in Zesty:
Fix Released
Bug description:
[Impact]
Nplan has been in active development and includes important bug fixes and
critical features for users.
[Test case]
- Run nplan integration tests on the release
- Validate that netplan generate && netplan apply alone, without config,
behave as expected (no result)
- Validate that netplan generate && netplan apply with minimal config writes
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
- Validate that netplan generate && netplan apply works with any existing
configuation.
[Regression potential]
Existing configurations should remain working with no changes. Possible
regressions might include failing to properly set routes for devices, or
applying custom configuration for bridge on bond devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1688632/+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
