Using latest MAAS trunk with Juju 1.24 or 1.25 will cause Juju to fail to bootstrap the node.
This issue is how Juju sets up /etc/network/interfaces. Specifically this code here:
https://github.com/juju/juju/blob/master/provider/maas/environ.go#L1131
In MAAS trunk what will be 1.9, custom network configuration is now supported. All static IP addresses are now assigned statically on the node instead of over DHCP. This is the default behavior that people want so that if the DHCP server goes down and the node lease expires that the IP address does not get removed.
Because of this it causes and issue with how Juju parses /etc/network/interfaces. Juju expects it to look specifically like
auto eth0
iface eth0 inet dhcp
Which is no longer the case and will very rarely will be the case, even by default it wont be. It will look like this.
auto eth0
iface eth0 inet static
address 192.168.122.10/24
gateway 192.168.122.1
When Juju is bootstrapped on that node the user-data that is ran by cloud-init changes that configuration to:
iface eth0 inet static
address 192.168.122.10/24
gateway 192.168.122.1
Notice how the "auto eth0" has been removed and the bridge was not created. When the networking is bounced on the node, eth0 will not come up and Juju will not be able to SSH in cause the bootstrap to fail and the node to be useless as no one can SSH in.
Bootstrapping with environment option "disable-network-management: true" allows bootstrapping to work and services can be deployed but obliviously this prevents the ability to deploy services to LXC containers.
Bootstrapping with the "address-allocation" feature flag also works and LXC containers can be used and are registered as devices in MAAS.
This most likely will affect 1.24, 1.25, and master. Retargeting.