action #125279
closed[security] test fails in verify_efi_mok - create_hdd_textmode_secureboot@aarch64 used to have different UEFI_PFLASH_VARS
100%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-QR-aarch64-aarch64_secureboot@aarch64 fails in verify_efi_mok. Last good: 172.1 (or more recent)
Unlike ticket #125264 where it was identified that a passing verify_efi_mok had UEFI_PFLASH_VARS = sle-15-SP4-aarch64-172.1-textmode@aarch64-uefi-vars_sb.qcow2 but now has UEFI_PFLASH_VARS = /usr/share/qemu/aavmf-aarch64-ms-vars.bin
... drumroll create_hdd_textmode_secureboot@aarch64 has it the other way around - it now has UEFI_PFLASH_VARS sle-15-SP4-aarch64-179.1-textmode@aarch64-uefi-vars.qcow2 while when also verify_efi_mok worked create_hdd_textmode_secureboot@aarch64 had (https://openqa.suse.de/tests/9881708#settings) UEFI_PFLASH_VARS /usr/share/qemu/aavmf-aarch64-ms-vars.bin
This could explain why there seems to be a mismatch between what state the image is when it's created vs what it's later expected to be at.
Updated by tjyrinki_suse almost 2 years ago
- Related to action #125264: [security] test fails in verify_efi_mok on 15-SP4 QU / aarch64 added
Updated by tjyrinki_suse almost 2 years ago
Here is a rerun of create_hdd_textmode_secureboot with the "right", old settings: https://openqa.suse.de/tests/10610240#
Updated by tjyrinki_suse almost 2 years ago
And here a run of aarch64_secureboot using that: https://openqa.suse.de/tests/10610763
Updated by pstivanin almost 2 years ago
- Status changed from New to In Progress
- Assignee set to pstivanin
Updated by pstivanin almost 2 years ago
- Status changed from In Progress to Rejected
- % Done changed from 0 to 100
This is not an issue, create_hdd_textmode_secureboot has always had those pflash code & vars.