CI breakage: Deployed nodes don't get a static IP address
Bug #1366726 reported by
Raphaël Badin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Julian Edwards |
Bug Description
The failure in http://
It seems that there is a race somewhere as it doesn't happen all the time.
Related branches
lp:~julian-edwards/maas/always-send-leases
- Jeroen T. Vermeulen (community): Approve
-
Diff: 602 lines (+220/-199)7 files modifiedsrc/maasserver/api/node_groups.py (+2/-58)
src/maasserver/api/tests/test_nodegroup.py (+0/-136)
src/maasserver/models/macaddress.py (+56/-1)
src/maasserver/models/node.py (+9/-0)
src/maasserver/models/tests/test_macaddress.py (+135/-1)
src/maasserver/models/tests/test_node.py (+17/-2)
src/maasserver/rpc/leases.py (+1/-1)
description: | updated |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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 d-jenkins. ubuntu- ci:8080/ view/MAAS/ job/utopic- adt-maas- manual/ 204/console
Console output: http://
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. 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/provisionin gserver/ pserv_services/ lease_upload_ service. py ).
- the leases parser kicks in: it reports the IP addresses *but* update_
- 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.