MAAS nodes should re-report the IP address they observe assigned to themselves at deployment time

[Mike Pontillo]

When I use MAAS with a DHCP server that MAAS does not manage, I see a DISCOVERED address when I commission the node (the IP address that commissioning reports back).

On a MAAS-managed network, the DHCP lease parser will update the DISCOVERED addresses based on the current state of the DHCP lease.

On an unmanaged network, this does not happen - so the IP address in the MAAS database is simply the "last seen at commissioning" IP address, which could change between commissioning and deployment.

Therefore, MAAS should update the DISCOVERED IP address at install time based on the new IP address received from the DHCP server.

[Mike Pontillo (mpontillo)]

This could be fixed in src/maasserver/api/pxeconfig.py, but it would require:

(1) trusting the web request that generates it. (which is probably okay)
(2) juggling the current DISCOVERED (observed) IP addresses around, which could be non-trivial. (are they IPv4 or IPv6? are they empty? are we sure they are linked to *just* the interface which claims to have been discovered?)

[Andres Rodriguez (andreserl)]

We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.