QA (public) » openQA Project (public) » openQA Tests (public)

Current state:
If we want to boot the systems with UEFI + secure boot, then the current default ovmf (code|vars) files we have in all the workers are not valid. We need new ones.
Fabian pointed me to some RPM where we can extract the ovmf file:
https://build.suse.de/projects/SUSE:SLFO:Main:Staging:Rings:1-MinimalX/packages/ovmf/repositories/standard/binaries
So, the rpm called ovmf-202305-slfo.1.3.17.x86_64.rpm contains the files we need to extract:

• ovmf-x86_64-devel-vars.bin
• ovmf-x86_64-devel-code.bin

I have extracted them and changed the namehttps://bugzilla.suse.com/show_bug.cgi?id=1228897https://bugzilla.suse.com/show_bug.cgi?id=1228897 to :

• ovmf-x86_64-staging-vars.bin
• ovmf-x86_64-staging-code.bin

And uploaded them to wotan.suse.de: https://w3.nue.suse.com/~jalausuch/ovmf/
Oliver has copied these files to all workers.
I have tried to boot a VM from a staging image but it doesn't boot, after telling RMs, Fabian created this bug:
https://bugzilla.suse.com/show_bug.cgi?id=1228897

So, we are now waiting for new uefi files to be used.

For now, I have disabled secure-boot in stagings using the following machine type: uefi-no-secboot which uses boot files without enabling secure-boot. This is a workaround to unblock the testing but not the final goal of this ticket.

The ideal case is that Release Managers provide a repository where Salt can pull the RPM from to install those files in the workers. Fabian suggested that this one could be used: https://build.suse.de/projects/SUSE:SLFO:Main:Staging:Rings:1-MinimalX/packages/ovmf/repositories/standard/binaries

Related slack threads:

• https://suse.slack.com/archives/C03G45KTP6W/p1722850993683269 -> this is where I am asking RMs to provide a tailored ovmf file for stagings
• https://suse.slack.com/archives/C02CANHLANP/p1722332804758019 -> asking tools team to copy the files to all the workers