action #62051
Updated by JERiveraMoya over 4 years ago
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).