action #120100
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Change validation for verifying secure boot after jsc#PED-1409
Description
Observation¶
The verify_secure_boot test is failing on Build 38.1.
Filed bsc#1205179 for that problem.
This commment is mentioning, that in the latest kernel the
deprecated evifars sysfs interface got removed. So no more efivars in Kernel >= 5.14.21-150500.24.
Since the whole test module relies on the existence of that sysfs interface, we cannot use it any more for SP5 and
we need to find another way to determine the status of secure boot.
Acceptance criteria¶
AC1: Find a new way to determine the status of secure boot for SLE >= 15-SP5.
Suggestions¶
jsc#PED-1409
We have a couple, perhaps just with the first changing the path is enough: bsc#1205179#c4 | bsc#1205179#c5
Updated by JERiveraMoya about 2 years ago
let's schedule it when we have some hint about the solution.
Updated by JERiveraMoya about 2 years ago
- Tags set to qe-yast-refinement
- Description updated (diff)
- Target version set to Current
Updated by JERiveraMoya about 2 years ago
- Subject changed from Rework verify_secure_boot test to Change validation for verifying secure boot after jsc#PED-1409
- Description updated (diff)
Updated by JERiveraMoya about 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by openqa_review about 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoyast_non_secure_boot@uefi
https://openqa.suse.de/tests/9970213#step/verify_secure_boot/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by geor about 2 years ago
- Status changed from Workable to In Progress
- Assignee set to geor
Updated by geor about 2 years ago
- Status changed from In Progress to Resolved