[2.0rc1] Unable to connect to BMC causes a traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Newell Jensen | ||
2.0 |
Fix Released
|
Low
|
Newell Jensen |
Bug Description
It seems that we were unable to connect to the BMC for a valid reason, unfortunately, this is causing a traceback that should not be there.
==> /var/log/
2016-07-08 10:50:34 [ClusterClient,
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
raise exc_type(
File "/usr/lib/
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
raise exc_info[
File "/usr/lib/
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/
File "/usr/lib/
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 43 lines (+5/-10)2 files modifiedsrc/provisioningserver/power/query.py (+5/-3)
src/provisioningserver/power/tests/test_query.py (+0/-7)
Changed in maas: | |
status: | Fix Committed → Fix Released |
After discussing this with the MAAS team we have decided that we are going to add Debug logging for the rack controller in a future release which will take care of the issue of seeing this traceback in the logs. That is, it will only show when the rack is in Debug mode.