just got a report of the same issue and resolution with 1.20.11 on orangebox maas. same s/br0/lxcbr0 fix for the container on machine 0. we tried again and got a slightly different issue on machine 2's container
oddly on machine 0 the container had br0 for the bridge, its also failing on machine 2 but the lxc container appears to be targeted towards the correct bridge.
just got a report of the same issue and resolution with 1.20.11 on orangebox maas. same s/br0/lxcbr0 fix for the container on machine 0. we tried again and got a slightly different issue on machine 2's container
Forensenic
status output -> https:/ /pastebin. canonical. com/119751/ /pastebin. canonical. com/119742/ /pastebin. canonical. com/119746/ /pastebin. canonical. com/119748/ /pastebin. canonical. com/119752/ /pastebin. canonical. com/119753/
failed container log output -> https:/
juju machine agent log -> https:/
cloudinit log -> https:/
ifconfig -> https:/
container config -> https:/
oddly on machine 0 the container had br0 for the bridge, its also failing on machine 2 but the lxc container appears to be targeted towards the correct bridge.