I've found a workaround for the issue to let me launch lxc containers via juju
After the first container fails to launch, ssh to the hypervisor edit /var/lib/lxc/juju-trusty-lxc-template/config change br0 -> lxcbr0 After editing the template config all subsequent lxc containers will launch via juju -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
