[2.5] When user clicks 'check power' over UI, errors are not logged
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
I was trying to debug issues with a BMC and noticed that when the user clicks 'check power' in the UI, errors are not logged in rackd.log.
If I try, however, to perform an action (such as commissioning), the error is logged in rackd.log (but they don't specify to which machine this applies).
File "/usr/lib/
system_id, hostname, power_type, power_change, context)
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
power_func, system_id, context)
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
inContext.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
amt_command = self._get_
File "/usr/lib/
'exception
provisioningse
So I think there's some improvements to be made here:
1. On *manual* check power, if there's error, it should be logged (and displayed in the UI. For the UI there's a different bug report [1])
2. Log should include which machine this was performed for.
Changed in maas: | |
importance: | Undecided → High |
importance: | High → Medium |
status: | New → Triaged |
milestone: | none → 2.5.0beta1 |
Changed in maas: | |
milestone: | 2.5.0beta1 → 2.5.0beta2 |
Changed in maas: | |
milestone: | 2.5.0beta2 → 2.5.0 |
Changed in maas: | |
milestone: | 2.5.0 → 2.5.x |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team