IPMI driver does not handle timeouts correctly
Bug #1508741 reported by
Andres Rodriguez
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Newell Jensen | ||
2.0 |
Fix Released
|
Critical
|
Gavin Panella |
Bug Description
MAAS is unable to reach the BMCs. However instead of correctly handling
the timeout, it is erroring out. The machines should show a RED for
power error in the UI, but this is not the case. They still show the
status before this issue (which was on). The machines are actually off.
Related branches
lp:~newell-jensen/maas/update-fix-1508741-1.9
- Lee Trager (community): Approve
-
Diff: 25 lines (+3/-1)2 files modifieddocs/changelog.rst (+2/-0)
src/provisioningserver/drivers/power/ipmi.py (+1/-1)
lp:~newell-jensen/maas/ipmi-regex-return-output-when-no-match
- Andres Rodriguez (community): Approve
-
Diff: 62 lines (+6/-12)2 files modifiedsrc/provisioningserver/drivers/power/ipmi.py (+3/-6)
src/provisioningserver/drivers/power/tests/test_ipmi.py (+3/-6)
lp:~allenap/maas/ipmi-power-confusion--bug-1560830
- Newell Jensen (community): Approve
- Andres Rodriguez (community): Needs Information
-
Diff: 49 lines (+15/-6)2 files modifiedsrc/provisioningserver/drivers/power/ipmi.py (+3/-6)
src/provisioningserver/drivers/power/tests/test_ipmi.py (+12/-0)
Changed in maas: | |
milestone: | none → 1.9.0 |
importance: | Undecided → Critical |
summary: |
- MAAS ipmi power does not handle timeouts correclt + IPMI driver does not handle timeouts correctly |
description: | updated |
description: | updated |
Changed in maas: | |
assignee: | nobody → Ricardo Bánffy (rbanffy) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
milestone: | 1.9.0 → 1.9.1 |
Changed in maas: | |
status: | In Progress → Triaged |
assignee: | Ricardo Bánffy (rbanffy) → nobody |
Changed in maas: | |
status: | Triaged → Incomplete |
Changed in maas: | |
milestone: | 1.9.1 → 1.9.2 |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A red power icon in the UI denotes that the power status could not be *queried*. This failure arises when trying to *change* the power state.
If the power change that fails was initiated as a result of a status change, e.g. when starting commissioning, the node should be transitioned to the corresponding failed state, e.g. failed commissioning. That will happen when the commissioning monitor times-out, but it may be that we can detect this failure sooner (or already do).
If the power change that fails was initiated by the user then the user is expected to see that the node did not power on or off and then investigate. A log entry is added to the node event log that will help.
This is not a bug.