1.8b6 Cannot mark a machine broken that is "deployed" and "on"
Bug #1456699 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
1. have a machine that is deployed and on
2. select that machine and choose "mark broken"
3. I get an error, saying "1 node cannot be marked broken. To proceed, update your selection. "
----
I should be able to mark a node broken independently of its state
and the current error notification doesn't explain why the action cannot be performed.
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)
Changed in maas: | |
milestone: | none → 1.8.0 |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.