"Start node" UI button does not allocate node before starting in 1.7
Bug #1365591 reported by
Dustin Kirkland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Graham Binns |
Bug Description
I'm trying to start a node for the first time in MAAS 1.7 GUI, and I'm unable to.
It turns out, I needed to allocate the node to myself, first, and then start it. This seems a little silly, and certainly not expected by an experienced MAAS 1.5 user.
If a user tries to start a node, and it's not already allocated to them, MAAS should just allocate it to them at that time.
Related branches
lp:~gmb/maas/start-and-allocate-bug-1365591
- Raphaël Badin (community): Approve
- Gavin Panella (community): Approve
-
Diff: 70 lines (+37/-2)2 files modifiedsrc/maasserver/node_action.py (+12/-2)
src/maasserver/tests/test_node_action.py (+25/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Low |
assignee: | Raphaël Badin (rvb) → nobody |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Graham Binns (gmb) |
summary: |
- allocate node (if not already allocated) when starting + "Start node" UI button does not allocate node before starting in 1.7 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This needed to be done to de-conflate the allocation and power operations, so that nodes may be powered off without deallocating. — you would want a "start node" that doesn't try to allocate in that case.
Suggestions:
- make the old "start node" button more intelligent, and auto-allocate as necessary
- change the label on the button depending on whether the node is allocated or not
any more?