API doesn't allow releasing when a node is in Failed Releasing or Failed Disk Erasing
Bug #1384821 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Jason Hobbs | ||
1.7 |
Fix Released
|
High
|
Jason Hobbs |
Bug Description
The API doesn't allow releasing when a node is in Failed Releasing or Failed Disk Erasing, even though it's perfectly reasonable to want to attempt the release operation again. The UI does allow Releasing when in these states.
Related branches
lp:~jason-hobbs/maas/allow-releasing-from-failed-states-lp-1384821
- Julian Edwards (community): Approve
- Christian Reis (community): Needs Information
-
Diff: 10 lines (+2/-0)1 file modifiedsrc/maasserver/models/node.py (+2/-0)
lp:~jason-hobbs/maas/allow-releasing-from-failed-states-lp-1384821-1.7
- Jason Hobbs (community): Approve
-
Diff: 10 lines (+2/-0)1 file modifiedsrc/maasserver/models/node.py (+2/-0)
lp:~andreserl/maas/update_changelog_1.7_pre_rc
- Andres Rodriguez (community): Approve
-
Diff: 21 lines (+12/-1)1 file modifieddebian/changelog (+12/-1)
Changed in maas: | |
milestone: | none → 1.7.0 |
status: | New → Triaged |
assignee: | nobody → Jason Hobbs (jason-hobbs) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
If it's already failed releasing/disk erasing, should we just treat that as
effectively released, and broken?