1.8b6 Cannot mark a ready node "Broken"
Bug #1456696 reported by
Carla Berkers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Blake Rouse | ||
Bug Description
In 1.8b6 I cannot mark a ready node "Broken".
I have to "Aquire" it first, which doesn't make sense since marking it "Broken" means I stop owning it.
We should make it possible to mark unowned nodes broken too.
Related branches
lp:~blake-rouse/maas/fix-1456696
- Mike Pontillo (community): Approve
-
Diff: 15 lines (+2/-0)1 file modifiedsrc/maasserver/node_action.py (+2/-0)
Revision history for this message
| Raphaël Badin (rvb) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| importance: | High → Medium |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| milestone: | none → 1.8.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.
Makes sense. "Broken" means: this doesn't work, please have an admin look at it… but it makes sense to be able to transition a "Ready" node to "Broken" although that shouldn't be the most common use case (you usually mark a node "Broken" after you try to actually use it).