Dasharo / open-source-firmware-validation

OSFV infrastructure with automated tests and scripts for managing test results
Apache License 2.0
9 stars 2 forks source link

Get Secure Boot Menu Construction returns wrong menu #154

Open m-iwanicki opened 11 months ago

m-iwanicki commented 11 months ago

Device

QEMU

RTE version

QEMU

Affected component(s) or functionality

No response

Brief summary

Get Secure Boot Menu Construction returns Advanced Secure Boot Keys Management menu instead of Secure Boot Configuration

How reproducible

Every time

How to reproduce

Bug also happens when using normal ubuntu.iso (for example with Ubuntu 22.04.03) installed or not.

Expected behavior

After resetting secure boot keys to default and returning to previous menu Get Secure Boot Menu Construction should return ${sb_menu} = ['Current Secure Boot State Disabled', 'Enable Secure Boot [ ]', 'Secure Boot Mode <Standard Mode>']

Actual behavior

Returns Advanced Secure Boot Keys Management menu ${sb_menu} = ['> Reset to default Secure Boot Keys', '> Erase all Secure Boot Keys', 'Individual key management:', '> PK Options', '> KEK Options', '> DB Options', '> DBX Options', 'v']

Link to screenshots or logs

image

Additional context

Doesn't happen when using ./scripts/ci/qemu-run.sh graphic firmware

Solutions you've tried

Fix: Adding Sleep 3s in lib/secure-boot-lib.robot file in Make Sure That Keys Are Provisioned keyword between Reset To Default Secure Boot Keys ${advanced_menu} and Exit From Current Menu. It takes about 2-3 seconds to reset keys to default after choosing yes in this step: image

m-iwanicki commented 10 months ago

Adding Read From Terminal Until Esc=Exit to the end of Reset To Default Secure Boot Keys should fix this issue (754c180), previous solution only worked in that one keyword.

macpijan commented 4 months ago

@BeataZdunczyk This can be grouped together with these big secure boot PRs. Added label to group similar issues together.