1.8b4: maas root node start distro_series=precise on a non-allocated node returns wrong error message
Bug #1449011 reported by
Larry Michel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Raphaël Badin |
Bug Description
If I try to start a node through CLI without first allocating the node, then I get an error message that tells user that wrong distribution was selected from a list of OSes that is actually an empty list.
ubuntu@
{"osystem": ["Select a valid choice. ubuntu is not one of the available choices."], "distro_series": ["Select a valid choice. ubuntu/precise is not one of the available choices."]}
It should say that the node wasn't allocated.
Not specifying distro_series results in powering on operation on the node.
Related branches
lp:~rvb/maas/start-bug-1449011
- Gavin Panella (community): Approve
-
Diff: 37 lines (+12/-1)2 files modifiedsrc/maasserver/api/nodes.py (+3/-0)
src/maasserver/api/tests/test_node.py (+9/-1)
Changed in maas: | |
importance: | Undecided → Low |
milestone: | none → 1.8.0 |
summary: |
- 1.8b3: maas root node start distro_series=precise on a non-allocated + 1.8b4: maas root node start distro_series=precise on a non-allocated node returns wrong error message |
Changed in maas: | |
assignee: | nobody → ubuntudotcom1 (ubuntudotcom1) |
tags: | added: cli |
Changed in maas: | |
assignee: | ubuntudotcom1 (ubuntudotcom1) → nobody |
assignee: | nobody → Raphaël Badin (rvb) |
Changed in maas: | |
status: | New → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Let's prioritize this to see if this fixes: https:/ /bugs.launchpad .net/maas/ +bug/1419041