[2.5, UI] Deploy KVM host - If the default deployment OS is non bionic+, clicking Register as MAAS KVM host doesn't set bionic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Anthony Dillon |
Bug Description
If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https:/
1. Import Xenial/Bionic images
2. Select Xenial as the deployment OS
3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic (see 02-clicking-
4. It allows it to be deployed without setting the OS (see https:/
The expected result is that when clicking 'Register MAAS KVM host' is clicked, 'bionic' is auto-selected as the latest available LTS.
PS. The information about LTS is already available in the commissioning OS< because the only supported commissioning OS are LTS.
Related branches
- Andres Rodriguez (community): Approve
- MAAS Lander: Approve
- Lilyana Videnova (community): Approve
-
Diff: 418 lines (+164/-148)6 files modifiedsrc/maasserver/static/js/angular/directives/os_select.js (+28/-37)
src/maasserver/static/js/angular/factories/nodes.js (+1/-2)
src/maasserver/static/js/angular/factories/tests/test_nodes.js (+4/-4)
src/maasserver/static/partials/node-details.html (+60/-44)
src/maasserver/static/partials/nodes-list.html (+65/-61)
src/maasserver/static/scss/_utils.scss (+6/-0)
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |