15.5 aarch64 awaiting grub entry but goot a console login instead
Grub screen does not appear, so boot_to_desktop fails while trying to assert it.
The grub screen timeout is set to -1 in parent job (disable_grub_timeout) which should have the effect to disable grub's timeout, and it seems to be the case after the first reboot: https://openqa.opensuse.org/tests/3132194#step/grub_test/1, also, in autoinst.log, we see the the -1 was sent to the SUT in disable_grub_timeout.
But, in the child job we can't see the grub screen at all, as if "enter" was typed.
We should test "manually" to understand what happens here.
openQA test in scenario opensuse-15.5-DVD-aarch64-yast2_nfs_v4_server@aarch64 fails in
Test suite description¶
NFS multi-machine test suite. Maintainer firstname.lastname@example.org
Fails since (at least) Build 408.2
Last good: 399.1 (or more recent)
Always latest result in this scenario: latest
#2 Updated by maritawerner 3 months ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
#5 Updated by JERiveraMoya 3 months ago
- Related to action #124805: test fails in disable_grub_timeout added
#6 Updated by JERiveraMoya 3 months ago
this happens due to https://progress.opensuse.org/issues/124805 because recent changes with shortcuts.
#7 Updated by openqa_review about 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: yast2_nfs_v4_server
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.