Comment 9 for bug 1483879

It happens with all nodes, not just bootstrap. destroy-environment does not
deallocate the container IPs.
On Aug 12, 2015 21:50, "Dimiter Naydenov" <email address hidden>
wrote:

> If you problem is only the bootstrap node, can you confirm there's no
> /etc/init/juju-clean-shutdown.conf with upstart or /etc/systemd/system
> /juju-clean-shutdown.service with systemd on the bootstrap node and/or
> its containers file systems' ?
>
> If the job is there in both host and containers, and the leases still
> leak, please attach machine-0*.log at DEBUG level at least.
>
> What are the bootstrap arguments and --debug log?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1483879
>
> Title:
> MAAS provider: terminate-machine --force or destroy-environment don't
> DHCP release container IPs
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1483879/+subscriptions
>