Comment 1 for bug 1366726

I think this is a real bug.

I put more debugging statements (https://code.launchpad.net/~rvb/maas/debug-level/+merge/233898) and ran the CI tests.

MAAS log: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas-manual/204/artifact/results/artifacts/maas-logs/var/log/maas/maas.log
Console output: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas-manual/204/console

You can see that only one of the 2 deployed nodes got a static IP address, the other one did not.

What I think happened is this:

- the nodes are booted up. They request an IP address from the DHCP server but are not yet enlisted.
- the leases parser kicks in: it reports the IP addresses *but* update_mac_cluster_interfaces discards the information (and thus doesn't create the network/cluster<->MAC connection) because the MACs are currently unknown (search for "Silently ignore MAC addresses that we don't know about" in src/provisioningserver/pserv_services/lease_upload_service.py ).
- the nodes enlist, the MACs are now known.
- the leases parser kicks in *but* it doesn't report the IP addresses back since it thinks that the leases haven't changed since last time (and it prints " No leases changed since last scan" in the log).

=> The result is that the connection MAC <-> cluster is never done and thus the node won't get an static IP address.