Comment 20 for bug 1473069

This is still a problem in Juju 2.0.1.
I deploy a complex network bundle and Juju does not default to any particular network and I get different network subnets from different machines/containers.

Even worse, in Juju 2.0.1 the bridges to eth0/1 fail and the containers start on the lxdbr0 interface on an isolated 10. network, that means the deployments now entirely fail.