Comment 2 for bug 1527068

I observe that as deployer calls Juju to add services, some of the machines that are requested of MAAS by Juju move into the 'allocated' state, rather than 'deploying' and later 'deployed' states. These machines never move out of 'allocated' and deployer eventually times out. The final status we get back from Juju has the error message 'Unable to allocate static IP due to address exhaustion.' Upon inspection of the /var/lib/maas/dhcp/dhcpd.leases file from the MAAS server, it does not appear that all IPs are actually used. The MAAS 1.8 Juju-QA test server has a static IP range configured from 10.0.80.102 to 10.0.80.250. One example of a failure, with logs, can be seen here:
http://reports.vapour.ws/releases/3464/job/maas-1_8-OS-deployer/attempt/718

Note, the active leases have been printed near the top of console log.