Disabling Disk Erasing with node in 'Failed Erasing' state leads to Invalid transition: Failed disk erasing -> Ready.
Bug #1381543 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Jason Hobbs | ||
Bug Description
To reproduce:
1) Enable Disk Erasing
2) Acquire a Node
3) Release the node
4) While the node is in Disk Erasing State, abort disk erasing.
5) The node is now in Failed Disk Erasing. Disable Disk Erasing
6) Release the node
You can work around this by marking the node as broken then fixed.
1.7.0~
Related branches
lp:~jason-hobbs/maas/fix-disk-erasing-to-ready
- Raphaël Badin (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 10 lines (+1/-0)1 file modifiedsrc/maasserver/node_status.py (+1/-0)
| Changed in maas: | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| assignee: | nobody → Jason Hobbs (jason-hobbs) |
| description: | updated |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
