cannot compose VM when static IP assigned is reserved in DNS

[Jeff Hillman]

MAAS 2.6.2
Bionic

If a previously created dnsresource exists, and a VM POD is composed with a static IP address that matches the ip_addresses value of that dnsresource, the POD VM compose fails because MAAS believes that the addresses is already in use.

The command:

    maas root pod compose 2 hostname=landscapeha-2 cores=2 memory=3072 storage=40.0 zone=3 interfaces=eth0:space=oam-space,ip=x.x.1.93,mode=static (scrubbed for customer security)

Fails with the message:

    The IP address x.x.1.93 is already in use.

Prior to running this command a dnsresource was created

    maas <profile> dnsresource create fqdn=landscape.customer.domain ip_addresses=x.x.1.93

FCE order of operations creates the fqdn's first and then the PODs, so this is breaking that. But either way, the address is in fact not used, it is just a DNS entry. There is no machine consuming this address at this time.

[Jeff Hillman (jhillman)]

To add to this, MAAS also fails to compose the VM if the requested IP address is in a reserved range.