A node can get stuck in the 'RELEASING' state if the power change command fails to power down the node.
Bug #1371033 reported by
Raphaël Badin
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
Bug Description
REALISING has no corresponding "failed" state. When the power command fails to power a 'RELEASING' node down (and that can happen for a variety of reasons), it crashes (http://
This is what I said would happen in my comment on https:/
Related branches
lp:~rvb/maas/refactor-states
- Gavin Panella (community): Approve
-
Diff: 144 lines (+17/-24)5 files modifiedsrc/maasserver/enum.py (+3/-3)
src/maasserver/models/node.py (+0/-6)
src/maasserver/models/tests/test_node.py (+0/-5)
src/maasserver/node_action.py (+10/-7)
src/maasserver/node_status.py (+4/-3)
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| tags: | added: landscape |
| Changed in maas: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think I misunderstood your comment on that MP then, I thought you were talking about RPC calls to mark the operation failed; instead what you were talking about is a total absence of a reply from the power ops.
It needs to be incorporated in the monitoring stuff I think.