After some testing, the systemd component does support a Priority= value
under the bridge port .network file and applies that.
Currently netplan does not accept port-priority
Something like:
bridges:
br0:
params:
port-priority:
eth1: 14
eth2: 28
And then further,
This bug was filed to address *port* priority, not the bridge priority.
As mentioned, systemd (networkd) lacks a per-port priority setting;
it should mirror path-cost which takes an interface and value, then the
interfaces have a [Bridge] section which has the value.
--
You received this bug
** No longer affects: systemd (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Unable to set bridge_portpriority with networkd
To manage notifications about this bug
This bug was fixed in the package systemd - 229-4ubuntu19
---
systemd (229-4ubuntu19) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and
Starting with systemd 229-4ubuntu17.
Observed:
Jul 19 13:25:17 key-giraffe systemd-networkd[467]:
[/etc/systemd/network/port1.network:6] Unknown lvalue 'Priority' in section
'Bridge'
Upgraded to systemd 229-4ubuntu19
Observed
/sys/class/net/port1/brport# cat priority
28
** Tags removed:
Hello Ryan, 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-4ubuntu19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
With systemd 229-4ubuntu17, attempting to set Bridge Por priority
results in:
Jul 12 10:28:13 systemd-sru-test systemd-networkd[1805]:
[/etc/systemd/network/port1.network:6] Unknown lvalue 'Priority' in
section 'Bridge'
And priority in sysfs is 32.
Upgrading to 229-4ubuntu18, restarting
Hello Ryan, 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-4ubuntu18
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
For the future, please include more analysis of the regression
potential. Remember: regression potential means you look at the code
changes and think of any possible places where regressions can appear,
even if they're really unlikely.
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu Yakkety)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Unable to set bridge_portpriority with networkd
To manage
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Unable to set bridge_portpriority with networkd
To manage
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
test_bridge_init (__main__.BridgeTest) ... ok
test_bridge_port_priority (__main__.BridgeTest) ... ok
test_bridge_port_priority_set_zero (__main__.BridgeTest)
It should be possible to set the bridge port priority to 0 ... ok
Passed on all architectures.
** Also affects: systemd (Ubuntu Yakkety)
Hello Ryan, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ * Netplan uses systemd-netword provider to configure all sorts of networking
settings
+ * However, unlike ifupdown, released versions of systemd do not support
setting bridgeport priority, aka
+ `brctl setportprio `
+ * This prevents full migration
** Also affects: systemd (Ubuntu Zesty)
Importance: Medium
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Upstream pull request:
https://github.com/systemd/systemd/pull/5545
Sample packages with patch applied for zesty:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2541
How to use:
Similar to bridge port cost, one can set [Bridge] Priority= setting in the
.network file for a given
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668347
Title:
Unable to set bridge_portpriority with networkd
To manage
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.03
--
20 matches
Mail list logo
