Project

General

Profile

action #120100

coordination #121876: [epic] Handle openQA review failures in Yam squad

Change validation for verifying secure boot after jsc#PED-1409

Added by rainerkoenig 3 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
High
Assignee:
geor
Target version:
Current
Start date:
2022-11-08
Due date:
% Done:

0%

Estimated time:

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

History

#1 Updated by JERiveraMoya 3 months ago

let's schedule it when we have some hint about the solution.

#2 Updated by JERiveraMoya 3 months ago

  • Priority changed from Normal to High

#3 Updated by rainerkoenig 3 months ago

  • Description updated (diff)

#4 Updated by JERiveraMoya 3 months ago

  • Tags set to qe-yast-refinement
  • Description updated (diff)
  • Target version set to Current

#5 Updated by JERiveraMoya 3 months ago

  • Subject changed from Rework verify_secure_boot test to Change validation for verifying secure boot after jsc#PED-1409
  • Description updated (diff)

#6 Updated by JERiveraMoya 3 months ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable

#7 Updated by openqa_review 2 months 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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

#8 Updated by geor 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to geor

#9 Updated by JERiveraMoya about 2 months ago

  • Parent task set to #121876

#10 Updated by geor about 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF