netplan 0.33 silently breaks bridge-priority
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan.io (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
1.
# lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
# cat /etc/cloud/
build_name: server
serial: 20180224
2.
# apt-cache policy nplan
nplan:
Installed: 0.33
Candidate: 0.33
Version table:
*** 0.33 500
500 http://
100 /var/lib/
3. netplan configuration creates a bridge with a priority value and matches
the value in /sys/class/
4. /sys/class/
--
The networkd renderer silently drops writing of Priority value to the [Bridge] section in a bridge's .netdev file.
The code says this:
netplan/
#if 0
/* FIXME: Priority= is not valid for the bridge itself, although it should work as the
* STP priority of the bridge itself. It's not supported by networkd, but let's
* keep it around in case it becomes supported in the future.
*/
if (def->bridge_
#endif
But bridge priority is settable via sysfs (with the bridge down) and via brctl setbridgeprio
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nplan 0.33
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Tue Feb 27 20:14:24 2018
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=C.UTF-8
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in nplan (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Fixed in netplan 0.34