Comment 15 for bug 1668347

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, once netplan has support for this syntax (which is almost
identical to path-cost)
Then cloud-init.net.netplan renderer will need an update to support
generating netplan yaml with
the correct structure.

On Wed, Nov 29, 2017 at 9:52 AM, Ryan Harper <email address hidden>
wrote:

> 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 notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1668347
>
> Title:
> Unable to set bridge_portpriority with networkd
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1668347/+subscriptions
>