Comment 24 for bug 1902425

I am very much suffering from this too. Completely unable to deploy new machines. 2.8/stable (2.8.4-8597-g.05313b458). I had unexplained unused ip addresses on two subnets inside dynamic ranges for managed networks, and one actual misconfigured switch management port inside a dynamic range. The misconfigured host has been reconfigured to be outside dynamic ranges. I have deleted the unknown-usage ip addresses and related interfaces using psql from maasserver_staticipaddress, maasserver_interface_ip_addresses, and maasserver_interfaces. I have tried unmanaging and re-managing all subnets. I've tried disabling and re-enabling DHCP. I've rebooted. I've removed and reinstalled the maas snap (I use a separate postgresql database as per production deployment instructions). I tried upgrading to 2.9/stable and then 2.9/edge but doing so breaks deployments via API, possibly due to an apparmor configuration bug (see #1917640). I have restored the postgresql database from a backup taken before 2.9 deployment and reinstalled maas 2.8/stable but the AUTO IP failure persists. So far nothing has worked.