[2.1] 'NoneType' object has no attribute 'external_dhcp'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
2016-09-24 18:41:47 [-] Unhandled failure dispatching AMP command. This is probably a bug. Please ensure that this error is handled within application code or declared in the signature of the b'
ReportForeignDH
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
f(*a, **kw)
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
File "/usr/lib/
key = error.trap(
File "/usr/lib/
File "/usr/lib/
raise self.value.
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
if interface.
Related branches
- Gavin Panella (community): Approve
-
Diff: 59 lines (+27/-4)2 files modifiedsrc/maasserver/rpc/rackcontrollers.py (+10/-3)
src/maasserver/rpc/tests/test_rackcontrollers.py (+17/-1)
Changed in maas: | |
milestone: | none → 2.1.0 |
importance: | Undecided → Critical |
summary: |
- 'NoneType' object has no attribute 'external_dhcp' + [2.1] 'NoneType' object has no attribute 'external_dhcp' |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
This is an interesting bug. We are getting a notification about an external DHCP server for an interface that appears to have no VLAN.
It's possible that this could occur if there is a race condition where the interface was disconnected for awhile, and the notification occurred in the 30-second window of time between when the interface was reconnected and when the MAAS region was notified of the change. But this seems unlikely.
I can put in a quick fix for the crash, but we should also look at the interfaces on your system, how they're modeled in MAAS, and which one would most likely report an external DHCP address.