Impossible to release a BROKEN node via the API.
Bug #1351451 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Graham Binns | ||
Bug Description
Broken nodes may not be released by calling the API 'release' method, though they can be released using the web UI.
Related branches
lp:~gmb/maas/test-poweroff-problem
- Julian Edwards (community): Approve
-
Diff: 92 lines (+36/-2)4 files modifiedsrc/maasserver/api.py (+6/-1)
src/maasserver/models/node.py (+7/-1)
src/maasserver/models/tests/test_node.py (+10/-0)
src/maasserver/tests/test_api_node.py (+13/-0)
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| importance: | Undecided → High |
| importance: | High → Medium |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug shouldn't arise, because marking a node broken automatically releases it, but rvba and I saw the bug on the orange boxes today. I suspect that's because there was some hackering going on on that orange box that wasn't using mark_broken() to mark the node broken, but this bug should still be fixed just in case.