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

ci/e2e: use Secure Boot for node provisioning #520

Merged
merged 3 commits into from
Nov 17, 2022
Merged

Conversation

ldevulder
Copy link
Contributor

@ldevulder ldevulder commented Nov 15, 2022

Secure Boot is now supported in Elemental and should be the default way to boot it. So E2E tests should also use SB.

Verification run: https://github.com/rancher/elemental/actions/runs/3487245310

@ldevulder ldevulder self-assigned this Nov 15, 2022
@ldevulder ldevulder marked this pull request as draft November 15, 2022 16:07
Secure Boot is now supported in Elemental and should be the default way
to boot it. So E2E tests should also use SB.

Signed-off-by: Loic Devulder <ldevulder@suse.com>
SMM is mandatory for UEFI Secure Boot on KVM.

Signed-off-by: Loic Devulder <ldevulder@suse.com>
Use 'smm-suse' version of UEFI firmware that contains the default SUSE
keys. This allow the already signed Elemental kernel to boot properly.

This commit also adds a UEFI vars template that contains a private
certificate used to be able to boot the provided and already signed iPXE
binary.

Signed-off-by: Loic Devulder <ldevulder@suse.com>
@ldevulder ldevulder marked this pull request as ready for review November 17, 2022 10:57
@ldevulder ldevulder merged commit a2758c3 into main Nov 17, 2022
@ldevulder ldevulder deleted the e2e-add-secure-boot branch November 17, 2022 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants