Comment 3 for bug 1418044

Chiming in as this burned 10 hours of pondering until I very clearly saw the issue watching the PXE boot show what I knew to be the incorrect MAAS IP for the cloud-config-url.

In my case, I was not using a laptop. I was using a server with a single port, two interfaces, one untagged and one tagging VLAN 100. The IP address on the VLAN 100 was no good for MAAS provisioning, but it was selected for the cloud-config-url over the untagged interface during setup. I'd like to note that the iSCSI setup used the IP address from the untagged interface.

So I second the motion to allow for entry of these IP addresses. The best of both worlds is a confirmation of discovered addresses. This let's the process be quick in terms of data entry reduction, but allows the operator to catch mistakes; rather than scratch their head for hours later. As I first stated, as soon as I saw the incorrect address in use I knew what was wrong, but I was never provided an opportunity to verify.

Cheers,