Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: Setting Default minimum kernel version for commissioning blocks deployments #4342

Closed
webteam-app opened this issue Aug 12, 2022 · 0 comments · Fixed by #4343
Closed

UI: Setting Default minimum kernel version for commissioning blocks deployments #4342

webteam-app opened this issue Aug 12, 2022 · 0 comments · Fixed by #4343
Assignees

Comments

@webteam-app
Copy link

Bug originally filed by alanbach at https://bugs.launchpad.net/bugs/1986372

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-20.04-edge.
  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-g.f0f96fa78 (Snap).

Thank you.

@huwshimi huwshimi self-assigned this Aug 15, 2022
huwshimi added a commit to huwshimi/maas-ui that referenced this issue Aug 15, 2022
Handle deploying machines when the default kernel is not in the default release.

Fixes: canonical#4342.
petermakowski pushed a commit that referenced this issue Aug 18, 2022
…4343)

Handle deploying machines when the default kernel is not in the default release.

Fixes: #4342.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants