Project

General

Profile

action #125279

Updated by tjyrinki_suse about 1 year ago

## Observation 

 openQA test in scenario sle-15-SP4-Online-QR-aarch64-aarch64_secureboot@aarch64 fails in [verify_efi_mok](https://openqa.suse.de/tests/10609863/modules/verify_efi_mok/steps/101). Last good: [172.1](https://openqa.suse.de/tests/10019854) (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 vs what it's later expected to be at.

Back