UI: Setting Default minimum kernel version for commissioning blocks deployments
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
| maas-ui |
Fix Released
|
Unknown
|
|||
Bug Description
This seems to be a UI issue and was reported by a client. I was able to easily reproduce it.
Steps to reproduce:
1. Set Commissioning OS/Kernel to: Focal/hwe-
2. Set Default Deployment image to a custom Ubuntu image.
3. Select a machine and perform "Deploy" action.
4. The screen is rendered with Custom Ubuntu image selected (As set in Step 2).
5. Click "Deploy".
6. An error message will be displayed similar to: "hwe-20.04-edge is not available for ubuntu/jammy on amd64/generic" (Screen shot attached).
If you switch the OS drop down on this screen back to Ubuntu then back to Custom, "Deploy" works.
The assumption here is that the UI is rendering a hidden field setting default kernel to the commissioning kernel and switching the OS drop down causes the kernel field to reset to "No minimum kernel", causing the custom image deployment action work afterwards.
Please let me know if there are any questions.
Tested Version: 3.2.2-12005-
Thank you.
| tags: | added: ui |
| Alan Baghumian (alanbach) wrote | #2 |
| Alan Baghumian (alanbach) wrote | #3 |
| Changed in maas-ui: | |
| importance: | Undecided → Unknown |
| status: | New → Fix Released |
| Changed in maas: | |
| status: | New → Fix Committed |
| Changed in maas: | |
| milestone: | none → 3.3.0 |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.3.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
Attaching regiond logs during the testing time frame. I have to region controllers and attaching the logs from both.