group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #14179
[Bug 1665088] Re: netplan bridge config doesn't support stp boolean
This bug was fixed in the package nplan - 0.23~16.04.1
---------------
nplan (0.23~16.04.1) xenial; urgency=medium
* Backport netplan 0.23 to 16.04. (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).
-- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx> Tue, 06 Jun 2017
17:19:10 -0700
** Changed in: nplan (Ubuntu Xenial)
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/1665088
Title:
netplan bridge config doesn't support stp boolean
Status in netplan:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in nplan source package in Xenial:
Fix Released
Status in systemd source package in Xenial:
New
Status in nplan source package in Yakkety:
Fix Committed
Status in systemd source package in Yakkety:
New
Status in nplan source package in Zesty:
Fix Released
Status in systemd source package in Zesty:
Fix Released
Bug description:
[Impact]
Users of netplan may wish to specify a custom MTU value for a device.
[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.
- Use the config below; ensure behavior is as expected (STP value is set on the interface; adjust device names as appropriate). There should be no errors at applying the requested configuration.
- Use the config below with the 'stp' key; the device should be brought up and include the default value set for the kernel.
[Regression potential]
STP default value should continue to be used for the bridge configured using netplan if STP is unset in configuration.
---
networkd supports setting STP value in Bridge type netdevs, but
netplan does not accept the key.
root@ubuntu:/etc/netplan# apt-cache policy nplan
nplan:
Installed: 0.18
Candidate: 0.18
Version table:
*** 0.18 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:/etc/netplan# lsb_release -rd
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04
root@ubuntu:/etc/netplan# cat 52-bridge.yaml
network:
ethernets:
eth0:
addresses:
- 10.11.12.13/24
match:
macaddress: '52:54:00:12:34:00'
set-name: foobar0
eth1:
match:
macaddress: '52:54:00:12:34:02'
set-name: eth1
eth2:
match:
macaddress: '52:54:00:12:34:04'
set-name: eth2
bridges:
br0:
addresses:
- 192.168.14.2/24
interfaces:
- eth1
- eth2
parameters:
ageing-time: 250
priority: 22
forward-delay: 1
hello-time: 1
max-age: 10
path-cost:
eth1: 50
eth2: 75
stp: true
version: 2
root@ubuntu:/etc/netplan# netplan generate
Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: unknown key stp
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1665088/+subscriptions