Unable to deploy Precise on a KVM node with MAAS 2.3.5

[Po-Hsu Lin]

It's been a while since we got the SRU request to test the Precise kernel, it works in the old days (at least for 3.2.0-139 ESM kernel)

But the deployment does not work for the 3.2.0-142 ESM proposed kernel.
The deployment will timeout with the 30min threshold.

I don't have any clue at hand other than that.

This is the output from /var/log/maas/maas.log:
Jul 22 10:00:11 xenialmaas maas.api: [info] Request from user jenkins to acquire a machine with constraints: [('name', ['precisetesting'])]
Jul 22 10:00:11 xenialmaas maas.node: [info] precisetesting: Status transition from READY to ALLOCATED
Jul 22 10:00:11 xenialmaas maas.node: [info] precisetesting: allocated to user jenkins
Jul 22 10:00:13 xenialmaas maas.node: [info] precisetesting: Status transition from ALLOCATED to DEPLOYING
Jul 22 10:00:13 xenialmaas maas.power: [info] Changing power state (on) of node: precisetesting (f4rfsc)
Jul 22 10:00:19 xenialmaas maas.power: [info] Changed power state (on) of node: precisetesting (f4rfsc)
Jul 22 10:00:31 xenialmaas maas.neighbour: [info] ens7 (physical) on xenialmaas: IP address 10.246.72.159 moved from 52:54:00:09:9b:6b to 52:54:00:a1:08:c8
Jul 22 10:06:49 xenialmaas maas.import-images: [info] Starting rack boot image import
Jul 22 10:06:49 xenialmaas maas.import-images: [info] Downloading image descriptions from http://10.246.72.216:5240/MAAS/images-stream/streams/v1/index.json
Jul 22 10:06:49 xenialmaas maas.neighbour: [info] ens7 (physical) on xenialmaas: IP address 10.246.72.159 moved from 52:54:00:a1:08:c8 to 52:54:00:09:9b:6b
Jul 22 10:06:50 xenialmaas maas.import-images: [info] Updating boot image iSCSI targets.
Jul 22 10:06:50 xenialmaas maas.import-images: [info] Finished importing boot images, the region does not have any new images.
Jul 22 10:06:50 xenialmaas maas.import-images: [info] Starting rack boot image import
Jul 22 10:21:47 xenialmaas maas.neighbour: [info] ens3 (physical) on xenialmaas: IP address 10.246.72.164 moved from 52:54:00:30:5f:fa to 52:54:00:7b:f7:32
Jul 22 10:21:47 xenialmaas maas.neighbour: [info] ens7 (physical) on xenialmaas: IP address 10.246.72.164 moved from 52:54:00:09:9b:6b to 52:54:00:7b:f7:32
Jul 22 10:26:49 xenialmaas maas.import-images: [info] Starting rack boot image import
Jul 22 10:26:49 xenialmaas maas.import-images: [info] Downloading image descriptions from http://10.246.72.216:5240/MAAS/images-stream/streams/v1/index.json
Jul 22 10:26:50 xenialmaas maas.import-images: [info] Updating boot image iSCSI targets.
Jul 22 10:26:50 xenialmaas maas.import-images: [info] Finished importing boot images, the region does not have any new images.
Jul 22 10:26:50 xenialmaas maas.import-images: [info] Starting rack boot image import
Jul 22 10:31:23 xenialmaas maas.node: [info] precisetesting: Releasing node
Jul 22 10:31:23 xenialmaas maas.node: [info] precisetesting: Status transition from DEPLOYING to RELEASING
Jul 22 10:31:23 xenialmaas maas.power: [info] Changing power state (off) of node: precisetesting (f4rfsc)
Jul 22 10:31:27 xenialmaas maas.node: [info] precisetesting: Status transition from RELEASING to READY

[Po-Hsu Lin (cypressyew)]

As per Sean's investigation, it looks like there is an IP conflict with another node.

Mark this bug as Invalid.

Thanks