The network config below closely reproduces the issue when a LXD VM is launched with it, has openvswitch-switch installed on it (e.g. via a manual DHCP on enp5s0), and is `cloud-init clean --logs --reboot`ed.
The log does not contain the error message, but calling `cloudinit.net.get_interfaces_by_mac()` from a Python console does trigger it.
If the vlans definition is removed, the instance comes up with networking (after the same reboot process).
The network config below closely reproduces the issue when a LXD VM is launched with it, has openvswitch-switch installed on it (e.g. via a manual DHCP on enp5s0), and is `cloud-init clean --logs --reboot`ed.
The log does not contain the error message, but calling `cloudinit. net.get_ interfaces_ by_mac( )` from a Python console does trigger it.
If the vlans definition is removed, the instance comes up with networking (after the same reboot process).
MAC_ADDRESS = "de:ad:be:ef:12:34"
interfaces :
macaddress : {0}
openvswitc h: {{}}
macaddress: {0} MAC_ADDRESS)
NETWORK_CONFIG = """\
bonds:
bond0:
interfaces:
- enp5s0
macaddress: {0}
mtu: 1500
bridges:
ovs-br:
- bond0
mtu: 1500
ethernets:
enp5s0:
mtu: 1500
set-name: enp5s0
match:
version: 2
vlans:
ovs-br.100:
dhcp4: true
id: 100
link: ovs-br
mtu: 1500
""".format(