Setting default_distro_series via "maas" command doesn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse | ||
1.8 |
Fix Released
|
High
|
Blake Rouse |
Bug Description
I haven't been able to set the default_
$ maas admin maas get-config name=default_
Success.
Machine-readable output follows:
"ubuntu"
$ maas admin maas get-config name=default_
Success.
Machine-readable output follows:
"trusty"
Checking the web UI, an undeployed node's page includes:
Operating System
Ubuntu 14.04 LTS "Trusty Tahr"
Now try setting the default distribution to a custom image that was previously imported:
$ maas admin maas set-config name=default_
Success.
Machine-readable output follows:
OK
$ maas admin maas set-config name=default_
{"default_
Following the directions and adding "custom/" to the specification seems to work:
$ maas admin maas set-config name=default_
Success.
Machine-readable output follows:
OK
Checking the result with get_config, though, shows that "custom/" is present in the string when it (or "ubuntu/") hadn't been before changing the setting:
$ maas admin maas get-config name=default_
Success.
Machine-readable output follows:
"custom/
(When setting the default_
Furthermore, the web UI now shows a confused default OS for an undeployed node, with a doubling-up of "custom/":
Operating System
custom/
An attempt to deploy the node shows OS dropdowns of "Custom" and "Ubuntu 14.04 GA (amd64)" -- note that the latter is a description associated with a DIFFERENT custom image than u14.04.2_amd64 -- namely, u14.04_amd64, on my system. Leaving those as-is results in a deployment of the u14.04_amd64 image, not the u14.04.2_amd64 image. I've also seen a completely failed deployment once or twice, but have been unable to pin down the precise circumstances to re-create that problem.
Similar results obtain when trying to set a different standard MAAS boot image (default_osystem of "ubuntu" with default_
I'm attaching my /var/log/maas directory tree as a tarball.
Here's my MAAS version information:
$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.8.0+bzr4001-
ii maas-cert-server 0.1.2-0~
ii maas-cli 1.8.0+bzr4001-
ii maas-cluster-
ii maas-common 1.8.0+bzr4001-
ii maas-dhcp 1.8.0+bzr4001-
ii maas-dns 1.8.0+bzr4001-
ii maas-proxy 1.8.0+bzr4001-
ii maas-region-
ii maas-region-
ii python-django-maas 1.8.0+bzr4001-
ii python-maas-client 1.8.0+bzr4001-
ii python-
Related branches
- Ricardo Bánffy (community): Approve
-
Diff: 178 lines (+126/-8)3 files modifiedsrc/maasserver/api/tests/test_maas.py (+75/-0)
src/maasserver/forms.py (+24/-2)
src/maasserver/forms_settings.py (+27/-6)
- Blake Rouse (community): Approve
-
Diff: 178 lines (+126/-8)3 files modifiedsrc/maasserver/api/tests/test_maas.py (+75/-0)
src/maasserver/forms.py (+24/-2)
src/maasserver/forms_settings.py (+27/-6)
Changed in maas: | |
status: | New → In Progress |
importance: | Undecided → High |
milestone: | none → 1.8.1 |
assignee: | nobody → Blake Rouse (blake-rouse) |
milestone: | 1.8.1 → 1.9.0 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |