** No longer affects: cloud-init (Ubuntu)
** Summary changed:
- Bridges fail to come online when configured via LXD, netplan, and cloud-init
+ Bridges without an address fail to come online with netplan+networkd
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that this is a workaround (specifying an address to
configure the bridge with):
lxc config set bionic-maas2 user.network-config "version: 2
ethernets:
eth0:
match:
name: eth0
dhcp4: true
eth1:
match:
name: eth1
bridges:
br0:
interfaces: [eth1]
Actually it might be nice in this case to, in fact, bind the carrier to
eth1.
In this scenario, I was planning on hanging other nested VMs and/or
containers on the virtual bridge inside the LXC. If the underlying link
was down for whatever reason, it would be more honest for that state to
I suspect that since you provided no network configuration to the
bridge, then it is considered unconfigured. networkctl seems to confirm.
Now, it looks like we could use:
BindCarrier=
A link name or a list of link names. When set, controls the behavior of the
current link. When all links in
