action #32449
closed[sle][functional][hard] test fails in reboot_gnome when grub timeout is activated
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-aarch64-cryptlvm@aarch64 fails in
reboot_gnome
After deleting soft failure bsc#1070233 it seems that reboot_gnome needs to be adaption when grub timeout is effectively disabled.
Reproducible¶
Fails since (at least) Build 486.4 (current job)
Expected result¶
Last good: https://openqa.suse.de/tests/1501879#step/disable_grub_timeout/2
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 6 years ago
- Subject changed from [sle][functional] test fails in reboot_gnome when grub timeout is activated to [sle][functional][hard][fast] test fails in reboot_gnome when grub timeout is activated
- Status changed from New to Workable
- Priority changed from Normal to High
Interesting. Yes, it seems that calling disable_grub_timeout completely - see https://openqa.suse.de/tests/1508919#step/disable_grub_timeout/11 - vs. https://openqa.suse.de/tests/1501879#step/disable_grub_timeout/1 in the "last good" seems to have triggered this. But why was it fine 13 days ago in https://openqa.suse.de/tests/1475457#step/reboot_gnome/13 then?
Updated by okurz about 6 years ago
- Due date set to 2018-03-27
- Target version set to Milestone 15
[fast] -> current sprint
Updated by riafarov about 6 years ago
- Subject changed from [sle][functional][hard][fast] test fails in reboot_gnome when grub timeout is activated to [sle][functional][hard] test fails in reboot_gnome when grub timeout is activated
Updated by mgriessmeier about 6 years ago
- Status changed from Workable to Rejected
it's not an issue with disable_grub_timeout, in https://openqa.suse.de/tests/1508919#step/reboot_gnome/16 we can see that password was typed ('SLOT 0 opened' appeared)
worked in the last 8 builds, didn't fail with this issue -> rejected, assuming that it won't happen again