Project

General

Profile

Actions

action #62051

closed

[functional][y] Automate AutoYaST option for non-secure boot

Added by JERiveraMoya over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
New test
Target version:
SUSE QA - Milestone 32
Start date:
2019-12-04
Due date:
2020-04-07
% Done:

0%

Estimated time:
Difficulty:

Description

After #61097 we can automate this check.

Acceptance criteria

New scenario uefi with non-secure boot is validated using attached profile

Suggestion

There are some places to check this option:

  • Install the system using startshell=1, so shell appears first time and we exit and the second time (after first phase autoyast installation) we can run efibootmgr -v. Maybe this step can be done in the installed system, so we can avoid to use startshell=1 and still check the output which is useful for debugging.
  • Installation overview show disable secure boot on Expert tab.
  • In the installed system od -An -t u1 /sys/firmware/efi/vars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c/data should return 0.

Further info

It seems that we need to use firmware for uefi with secure boot disable as well (when testing manually it was used qemu by command line instead of Virtual Manager but in openQA should not be problem I guess).


Files

ay_non_sec.xml (2.28 KB) ay_non_sec.xml JERiveraMoya, 2020-01-13 09:06
Actions

Also available in: Atom PDF