Project

General

Profile

Actions

action #26978

closed

autoyast/gnome installation stuck on grub

Added by dimstar about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Start date:
2017-10-24
Due date:
2017-11-08
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_reinstall_gnome@64bit fails in
installation

Reproducible

Fails since (at least) Build 20171022 (current job)

Expected result

Last good: 20171021 (or more recent)

Further details

Always latest result in this scenario: latest

Background

This test was long failing on https://bugzilla.opensuse.org/show_bug.cgi?id=1053863, which is now addressed
Snapshot 1021 passed it, and since 1022 it is failing again (but definitively with a new issue)

From what I understood, we disable the grub timeout now - but the autoyast setup test is not aware that it might have to confirm grub and expects grub to move on and reach a desktop without manual interaction

NOTE: this is not true for all autoyast setups, but only for the one created as a clone from a running system. The autoyast profiles published in openQA directly do not cause grub to stop


Related issues 1 (0 open1 closed)

Related to openQA Tests (public) - action #25658: [sle][functional][migration][opensuse][virtualization]Increase/disable timeout of initial grub menue to ensure tests do not miss itResolvedJERiveraMoya2017-09-292017-10-25

Actions
Actions #1

Updated by okurz about 7 years ago

  • Related to action #25658: [sle][functional][migration][opensuse][virtualization]Increase/disable timeout of initial grub menue to ensure tests do not miss it added
Actions #2

Updated by JERiveraMoya about 7 years ago

  • Assignee set to JERiveraMoya
Actions #3

Updated by JERiveraMoya about 7 years ago

  • Due date set to 2017-11-08
  • Status changed from New to In Progress
  • Target version set to Milestone 11
Actions #4

Updated by JERiveraMoya about 7 years ago

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3795
Needle added in the code to the loop that handle the set of potential matches. "ret" key sent when matching the grub screen to be able to continue to the next screen, the Desktop.

Actions #5

Updated by okurz about 7 years ago

that did not seem to work yet. E.g. see https://openqa.opensuse.org/tests/513659#step/installation/14 . The test finds "bios-boot" and therefore aborts the loop. Now the new tag you added is not checked anymore. Can you take a look again please?

Actions #6

Updated by JERiveraMoya about 7 years ago

It is looping in second stage of this test. In my local machine hitting 'ret' in first stage solved the problem, but prod environment seems to have different speed and in the test code both loops have similar exit-condition. I can also add the condition in second stage to avoid this problem.

Actions #7

Updated by JERiveraMoya about 7 years ago

bootloader is not included as exit condition of any of both stages in the test, as we want to end the test with gnome desktop.
Problem with hitting 'ret' only on first stage:

  • Local machine: only works on local because is going faster and does not match bios needle and instead it matches the bootloader needle, in turn hitting 'ret' and going to stage 2 and finds the desktop successfully.
  • Prod: on production matches bios first and exists first stage without possibility to hit 'ret' in second stage. PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3809 Regarding my local test: http://10.100.51.227/tests/263# autoyast_reboot test seems to be broken too.
Actions #8

Updated by JERiveraMoya about 7 years ago

PR to fix next error seen locally in this test: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3816

Actions #9

Updated by okurz about 7 years ago

PR merged, job triggered: https://openqa.opensuse.org/tests/516500

Actions #10

Updated by JERiveraMoya about 7 years ago

It looks resolved.

Actions #11

Updated by JERiveraMoya about 7 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF