I've had it confirmed that the leases file is authoritative, not the MAAS dhcplease database table - so my previous assertions about dhcp release from inspecting the database are flawed.
However, from investigation it seems that neither an lxc-stop from outside the container, nor a "halt" from inside the container, cause a dhcp release. An explicit "ifdown" from inside the container *does*. So it seems like the shutdown sequence does not do an "ifdown". Investigating further. (To see if we *should* be seeing this as Stephane asserted, and if so why it isn't happening, if not to see what it would take for us to add it to the shutdown.)
I've had it confirmed that the leases file is authoritative, not the MAAS dhcplease database table - so my previous assertions about dhcp release from inspecting the database are flawed.
However, from investigation it seems that neither an lxc-stop from outside the container, nor a "halt" from inside the container, cause a dhcp release. An explicit "ifdown" from inside the container *does*. So it seems like the shutdown sequence does not do an "ifdown". Investigating further. (To see if we *should* be seeing this as Stephane asserted, and if so why it isn't happening, if not to see what it would take for us to add it to the shutdown.)