Comment 8 for bug 1902425

To give a bit of context, MAAS tries up to 3 times to assign AUTO IPs when deploying, and checks if those IPs are available.

If the check fails, it usually means those IPs are currently in use by something that MAAS doesn't know about (e.g. machines with statically-assigned IPs in a subnet where MAAS controls DHCP).

If the deploy is retried, MAAS will skip those IPs as it now knows they're in use.
This could be a workaround, but of course deploy will fail if the next 3 IPs are also in use.

Ideally, IP shouldn't be assigned outside of MAAS if the subnet has DHCP managed by MAAS.