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/ failed container log output -> https://pastebin.canonical.com/119742/ juju machine agent log -> https://pastebin.canonical.com/119746/ cloudinit log -> https://pastebin.canonical.com/119748/ ifconfig -> https://pastebin.canonical.com/119752/ container config -> https://pastebin.canonical.com/119753/ 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. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
