MAAS 1.8 fails to find a cluster interface when an off-network node boots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Mike Pontillo |
Bug Description
Observed behavior[1]:
File "/usr/lib/
user_data = get_curtin_
File "/usr/lib/
network_config = compose_
File "/usr/lib/
'netmasks': map_netmasks(node),
File "/usr/lib/
interfaces, IPAddress(sip.ip))
File "/usr/lib/
if ip_address in interface.network:
TypeError: argument of type 'NoneType' is not iterable
Expected behavior:
MAAS finds the cluster interface based on the fact that it is within an unmanged dynamic range.
Related branches
- Blake Rouse (community): Approve
-
Diff: 74 lines (+51/-2)2 files modifiedsrc/maasserver/models/macaddress.py (+23/-2)
src/maasserver/models/tests/test_macaddress.py (+28/-0)
Changed in maas: | |
milestone: | none → 1.8.4 |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
status: | Triaged → Won't Fix |
After I worked around this issue (by changing find_cluster_ interface_ responsible_ for_ip( ) to ignore networks whose value is None, and checking the static/dynamic range for each cluster interface), I found that I could not delete nodes on this unmanaged subnet, because I would get this error:
Node failed to be deleted, because of the following error: DHCPv4 server is disabled.
From regiond.log:
2015-11-23 19:31:44 [HTTPChannel, 0,172.16. 100.10] Unhandled Error ver.rpc. exceptions. CannotRemoveHos tMap: DHCPv4 server is disabled.
Traceback (most recent call last):
Failure: provisioningser