Comment 8 for bug 1581250

What most likely happened was, when MAAS tried to communicate the lease deletion to the DHCP server, either the cluster (rack) controller or the DHCP server was not able to be reached. Therefore MAAS thought the lease was deleted, but DHCP still believed it was a static lease assigned to that MAC.

This is fixed by design in MAAS 2.0. We no longer rely on DHCP to maintain the state of static leases. (as part of the HA changes for MAAS 2.0, MAAS now fully manages the static leases rather than relying on DHCP to maintain that state.)

At this time, we don't have a plan to port the fix to MAAS 1.9, so marking this "Won't Fix" for MAAS 1.9.