MAAS UI bug: unable to deploy custom images without reselecting default
Bug #2020399 reported by
Ethan Myers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
| maas-ui |
Triaged
|
Low
|
Nick De Villiers | ||
| 3.2 |
New
|
Undecided
|
Unassigned | ||
| 3.3 |
New
|
Undecided
|
Unassigned | ||
| 3.4 |
Triaged
|
Low
|
Nick De Villiers | ||
Bug Description
In MAAS 3.2.7, MAAS will not allow you to deploy a custom image without selecting the default image first.
This custom image is selected as the default in MAAS settings (Settings > Deploy > Default operating system used for deployment). Clicking on cloud init, then clicking off the default setting and re-selecting will allow the image to deploy.
I've attached a video of the behavior.
https:/
| tags: | added: ui |
| Changed in maas: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Anton Troyanov (troyanov) wrote | #1 |
| Changed in maas: | |
| milestone: | none → 3.2.x |
| Changed in maas-ui: | |
| milestone: | none → 3.2.x |
| Changed in maas: | |
| importance: | Medium → Low |
| Changed in maas-ui: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in maas-ui: | |
| assignee: | nobody → Nick De Villiers (nickdv99) |
| milestone: | 3.2.x → 3.5.0 |
To post a comment you must log in.
Ethan, thanks for spotting this issue.
FTR:
From the video it is clear that this is a UI bug, probably something flaky with the state of the controls?