networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID

Bug #1715131 reported by Dimitri John Ledkov on 2017-09-05
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Undecided
Unassigned
Xenial
Undecided
Unassigned

Bug Description

[Impact]
Newer releases of networkd support more optional settings for Bridge Priority, AgeingTimeSec and DefaultPVID.

https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#AgeingTimeSec=
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#Priority=
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID=

Backporting these features to xenial, allows to use/set these options via netplan for any releases as for example deployed by MAAS.

[Fix]
cherrypick these settings for better supportability of networkd on xenial with netplan.

[Testcase]
1) Create .netdev bridge device
2) Specify Priority, AgeingTimeSec, DefaultPVID settings in the [Bridge] section
3) Verify that there are no parsing errors in journalctl from systemd-netword
4) Verify with `ip` command that the bridge device got created
5) Verify in sysfs that the settings requested have been applied to the device

[Regression]
These stanazas are optional, and will be ignored by older networkd if for example users start using them, and downgrade networkd to the one in release pocket. It is future compatible settings that will not cause upgrade issues, nor could result in failure to create the bridge device.

Changed in systemd (Ubuntu):
status: New → Fix Released
Changed in systemd (Ubuntu Xenial):
status: New → In Progress

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

description: updated

Hello Dimitri, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in systemd (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-xenial
Dimitri John Ledkov (xnox) wrote :

checked with 229-4ubuntu20 aging and priority parsed and set correctly, DefaultPVID is parsed correctly but not set. Will fix DefaultPVID setting in the next SRU. This SRU thus doesn't regress any settings and has only partial DefaultPVID key support.

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers