[UI/Papercut] Deploy: Selecting "Register as MAAS KVM host" overrides user OS selection without confirmation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Unassigned |
Bug Description
UI/Papercut bug
Note: it can be argued this isn't a bug -- but I certainly encountered it as a first-time user of MAAS.
MAAS host OS: Ubuntu 18.04.3 (x86_64) MAAS version: 2.6.0 (7802-g59416a86
How to reproduce: Given a machine is in a "Ready" state (i.e. commissioned and ready to be deployed)
1. Navigate to the machine's "Deploy" page (e.g. /MAAS/#
2. For "Choose your image", select the following options:
- Ubuntu
- 19.04 "Disco Dingo"
- Default kernel
For "Additional installs" select:
- (enable) Register as MAAS KVM host
3. Click the "Deploy machine" button
Bug: the release 19.04 was selected, but selecting "Register as MAAS KVM host" will force the host OS installed to be 18.04LTS -- without notifying the user.
Expected behaviour: Prompt the user that "Register as MAAS KVM host" requires the deployed OS to be 18.04LTS (or other LTS).
Related branches
- MAAS Lander: Approve
- MAAS UI team: Pending requested
-
Diff: 299 lines (+90/-123)5 files modifiedsrc/maasserver/static/js/angular/factories/nodes.js (+8/-13)
src/maasserver/static/js/angular/factories/tests/test_nodes.js (+15/-38)
src/maasserver/static/js/angular/services/osblacklist.js (+4/-1)
src/maasserver/static/partials/node-details.html (+28/-36)
src/maasserver/static/partials/nodes-list.html (+35/-35)
tags: | added: ui |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | none → next |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | next → 2.7.0b1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |