action #128621
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
[sporadic] Ensure to process grub from tianocore
Description
Motivation¶
Do not miss to process grub in these particular scenarios with tianocre to avoid failure in migrations:
sle-15-SP5-Migration-from-SLE15-SPx-aarch64-ha_migration_offline_dvd_sles15sp2_ltss@aarch64 fails in
grub_test
https://openqa.suse.de/tests/11029217#step/grub_test/37
(this is a different one where might need to send key 't'
Acceptance criteria¶
AC1: Ensure to process grub from tianocore not sending some accidental key
AC2: Figure out why send key 't' is required in the other failure
Suggestion¶
Debug sub handle_uefi_boot_disk_workaround most likely we are sending ret key there accidentally and going directly to login prompt
Updated by JRivrain over 1 year ago
- Tags set to qe-yam-refinement
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests) - Priority changed from Normal to High
Updated by JERiveraMoya over 1 year ago
- Tags deleted (
qe-yam-refinement)
we don't use anymore qe-yam-refinement.
Updated by JERiveraMoya over 1 year ago
- Subject changed from Grub looks wrong when booting from tianocore menu for multiple tests in migration, sporadically to [sporadic] Ensure to process grub from tianocore
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from High to Normal
- Target version set to Current
- Parent task set to #121876
I will add your description as a comment to the ticket, too many questions there:
Grub looks wrong when booting from tianocore menu for multiple tests in migration, sporadically. we are getting "welcome to grub! - Please press 't' to show the boot menu on this console".
We need to figure out what is trigerring this. Maybe Grub menu is appearing but we can't see it, normally it should have timeout disabled but we see [here](https://openqa.suse.de/tests/11022525#step/grub_test/1) that it is not, instead there is a 60 seconds timeout.
It is not easy to say what happens from just looking at the test result:
- did openqa stall for more than 60 seconds ?
- did the "enter" key still be pressed at that moment from previous step ?
- is it a virtualization issue that prevents the bootloader from being loaded properly ?
- is it a bug in grub that appears sporadically ?
Updated by leli over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to leli
Updated by leli over 1 year ago
Clone job to get video, http://openqa.suse.de/tests/11063279#
Updated by leli over 1 year ago
In fact, this issue is for the grub2 timeout hasn't been set correctly which caused grub2 can't be catched, so need set the workaround for bsc#1129504 as SOFTFAIL_1129504=1.
MR submitted, https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/294
Updated by leli over 1 year ago
- Status changed from In Progress to Resolved
MR merged, verified on latest build 100.1 https://openqa.nue.suse.com/tests/11116055#step/disable_grub_timeout/4
Updated by leli over 1 year ago
New MR for the same issue on build 101.1, https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/299