`machine deploy` parameter expectations and error output are not consistent
Bug #1662361 reported by
Ryan Beisner
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Dougal Matthews | ||
Bug Description
`machine deploy` parameter expectations and error output are not consistent.
### Probe
⟫ maas maas machine deploy qmwcqs distro_
{"distro_series": ["'?' is not a valid distro_series. It should be one of: '', 'ubuntu/trusty', 'ubuntu/xenial', 'ubuntu/yakkety', 'ubuntu/zesty'."]}
(Failed, but I discovered advice on what to set for a value.
### Try based on error from probe
⟫ maas maas machine deploy qmwcqs distro_
{"distro_series": ["xenial in distro_series does not match with operating system ubuntu"]}
(Failed, what huh?)
### Try with s.w.a.g.
⟫ maas maas machine deploy qmwcqs distro_
(Success, but not in line with what the cli just advised.)
Related branches
~d0ugal/maas:bug/1662361
- MAAS Lander: Approve
- Alberto Donato (community): Approve
-
Diff: 45 lines (+22/-1)2 files modifiedsrc/maasserver/api/tests/test_machine.py (+21/-0)
src/maasserver/forms/__init__.py (+1/-1)
| tags: | added: papercut |
| Changed in maas: | |
| milestone: | none → 2.3.0 |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| summary: |
- `machine deploy` parameter expectations and error output are not - consistent + [2.x, api] `machine deploy` parameter expectations and error output are + not consistent |
| tags: | added: api |
| Changed in maas: | |
| milestone: | 2.3.0 → 2.3.x |
Revision history for this message
| Joshua McClintock (jmcclintock777) wrote Re: [2.x, api] `machine deploy` parameter expectations and error output are not consistent | #1 |
Revision history for this message
| Joshua McClintock (jmcclintock777) wrote | #2 |
| summary: |
- [2.x, api] `machine deploy` parameter expectations and error output are - not consistent + `machine deploy` parameter expectations and error output are not + consistent |
| Changed in maas: | |
| milestone: | 2.3.x → 2.8.0b1 |
| Changed in maas: | |
| milestone: | 2.8.0b1 → 2.8.0b2 |
| Changed in maas: | |
| milestone: | 2.8.0b2 → 2.8.0rc1 |
| Changed in maas: | |
| milestone: | 2.8.0b3 → 2.8.0rc1 |
| Changed in maas: | |
| assignee: | nobody → Dougal Matthews (d0ugal) |
| Changed in maas: | |
| milestone: | 2.8.0b4 → 2.8.0rc1 |
| Changed in maas: | |
| status: | Triaged → 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.
This may be a similar issue, I have multiple types of distro_series per OS type:
maasuser@host:~# maas admin machine deploy hahnnk distro_
{"distro_series": ["'?not-sure?' is not a valid distro_series. It should be one of: '', 'esxi/6.7', 'esxi/6.7dell', 'esxi/6.7hpe', 'rhel/7', 'ubuntu/bionic', 'windows/win2016*', 'windows/
maasuser@host:~# maas admin machine deploy hahnnk distro_
{"distro_series": ["6.7hpe in distro_series does not match with operating system esxi"]}
It looks like it splits in the distro_series on '/' and takes the left side (esxi). How do I specify the right side '6.7/hpe'?