Netplan optional-addresses produces Unknown key name 'OptionalAddresses'

Bug #1880029 reported by Matt LaPlante
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
netplan.io (Ubuntu)
Triaged
Medium
Unassigned
Kinetic
Won't Fix
Medium
Unassigned

Bug Description

Running on 20.04 (focal), the following netplan config for a bridge interface, rendering with networkd:

network:
  version: 2
  bridges:
    br0:
      interfaces: [bond0, guest]
      dhcp4: on
      macaddress: aa:bb:cc:dd:db:2f
      optional-addresses: [ dhcp4 ]

Appears to apply cleanly, however under the hood, networkd appears to reject the resulting OptionalAddresses setting:

May 21 16:25:50 hyper systemd-networkd[864186]: /run/systemd/network/10-netplan-br0.network:5: Unknown key name 'OptionalAddresses' in section 'Link', ignoring.

Lukas Märdian (slyon)
tags: added: rls-kk-incoming
Changed in netplan.io (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
tags: added: fr-2440
tags: removed: rls-kk-incoming
Lukas Märdian (slyon)
tags: added: foundations-todo
Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.

Changed in netplan.io (Ubuntu Kinetic):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.