-
Notifications
You must be signed in to change notification settings - Fork 991
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
Fixes #37566 - Add UEFI Secure Boot Firmware to Libvirt #10321
base: develop
Are you sure you want to change the base?
Conversation
Failing tests should be fixed automatically after fog/fog-libvirt#155 is merged. |
As noted in my comment on the VMware-related PR #10324 (comment), the same issue occurs with Libvirt. The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few comments + it looks like failing tests are related.
Otherwise I was able to provision the Fedora 39 machine with BIOS, UEFI, and UEFI + Secure Boot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍏 LGTM
The fog-libvirt part has to be merged and released first
Oh I missed the failing tests:
This needs to be fixed. |
As I mentioned here, this should be fixed automatically after fog/fog-libvirt#155 is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't tested this myself, but the code reads well to me and the packaging side is correct.
@stejskalleos leaving the merge to you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test failures look related though. I think it's trying to make a connection to a real libvirt system, but haven't investigated.
Yes, you are correct. I'm looking into that now. |
For me, the libvirt connection errors are also happening in my PR (#10351), where I don't touch Libvirt at all. |
The connection errors are unrelated to the changes in this PR. |
Normally, I would proceed with a merge, but in this case, I would prefer to fix tests first and then merge PRs. |
The tests are running without any errors in my local environment, but I can fix them if you'd prefer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests are running without any errors in my local environment, but I can fix them if you'd prefer.
Nah, let's get this in, it's been tested by multiple people, I think it's safe.
@nofaralfasi the Redmine issue check is failing, can you please squash the comments? I can't overpass that check. |
- Add Firmware option to Libvirt VM creation. - Added a new firmware type for Secure Boot. - Enable `enrolled-keys` by default when Secure Boot is activated. - Added firmware-related methods to the ComputeResource model for shared use between VMware and Libvirt.
The failing tests in this PR |
Libvirt test failures are fixed here: #10377 |
I approved PR, resolved all comments and yet still can't merge the issue :( |
@stejskalleos there's a packaging change, but we already merged that. If you rebase then I'd expect it to be possible. |
Requires:
This PR includes two commits:
When creating a new host in Foreman, after selecting
Libvirt
as the compute resource, a new option to select the VM's firmware will appear under theVirtual Machine
tab. See the screenshot below for a demonstration:Notes:
enrolled-keys
are enabled by default when Secure Boot is activated.loader secure='yes'
setting.For more details: community post.