Project

General

Profile

Actions

action #117700

open

[qe-sap][y] Grub error: Stuck in "Welcome to Grub!" on PowerVM

Added by rainerkoenig over 1 year ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-10-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP5-Migration-from-SLE15-SPx-ppc64le-offline_sles15sp2_ltss_media_basesys-srv_all_full_pre@ppc64le-hmc-single-disk fails in
bootloader

Instead of showing a GRUB menu the bootloader seems to try a TFTP boot and fails. Previous build 24.1 did show a GRUB menu:
https://openqa.suse.de/tests/9564819#step/bootloader/17

Other failuse in the Migration job group:
https://openqa.suse.de/tests/9682577#step/bootloader/17
https://openqa.suse.de/tests/9680420#step/bootloader/17
https://openqa.suse.de/tests/9680442#step/bootloader/17
https://openqa.suse.de/tests/9680479#step/bootloader/17

Problem is spread over various job groups and also seen in the YaST Review:
https://openqa.suse.de/tests/9678721#step/bootloader_start/17
https://openqa.suse.de/tests/9681333#step/bootloader_start/17
https://openqa.suse.de/tests/9679952#step/bootloader_start/17
https://openqa.suse.de/tests/9680258#step/bootloader_start/17
https://openqa.suse.de/tests/9680264#step/bootloader_start/17
https://openqa.suse.de/tests/9680270#step/bootloader_start/17

Reproducible

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

Interesting detail is that only a part of the bootloader failures seem to be this problem wth trying TFTP.
There are other tests that show the GRUB bootmenu but then fail at a later step while typing the grup parameters
amd then get "error: timeout reading".

What the problems have in common is that they seem to occur on ppc64le-hmc-single-disk and ppc64-hmc-4disk only.

Expected result

Last good: 24.1 (or more recent)


Related issues 1 (1 open0 closed)

Related to openQA Tests - action #117808: [qe-sap][y] Grub error: Timeout reading in bootloader on PowerVMNew2022-10-10

Actions
Actions #1

Updated by maritawerner over 1 year ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Project changed from qe-yam to openQA Infrastructure
Actions #3

Updated by okurz over 1 year ago

  • Related to action #117808: [qe-sap][y] Grub error: Timeout reading in bootloader on PowerVM added
Actions #4

Updated by okurz over 1 year ago

  • Project changed from openQA Infrastructure to openQA Tests
  • Subject changed from openQA test fails in bootloader, bootloader_start to [qe-sap][y] openQA test fails in bootloader, bootloader_start
  • Category set to Bugs in existing tests

This sounds very much related to #117808, same reasoning for assignment

Actions #5

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: lvm+cancel_existing_cryptlvm@ppc64le-hmc-single-disk
https://openqa.suse.de/tests/9775466#step/bootloader_start/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #6

Updated by JERiveraMoya over 1 year ago

  • Status changed from New to Rejected

This is a different issue, but also reflect the issue with network.

Actions #7

Updated by JERiveraMoya over 1 year ago

  • Status changed from Rejected to New
Actions #8

Updated by JERiveraMoya over 1 year ago

  • Subject changed from [qe-sap][y] openQA test fails in bootloader, bootloader_start to [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" in PowerVM
Actions #9

Updated by JERiveraMoya over 1 year ago

  • Subject changed from [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" in PowerVM to [qe-sap][y] Grub error: Stuck in "Welcome to Grub!" on PowerVM
Actions #10

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: autoupgrade_sles15sp2_ltss_scc_basesys-srv-lp-tsm_def_full_ssh_auto_pre
https://openqa.suse.de/tests/10088398#step/bootloader/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #11

Updated by openqa_review about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles15sp2_ltss_media_basesys-srv_all_full_pre
https://openqa.suse.de/tests/10220104#step/bootloader/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions #12

Updated by openqa_review 11 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: RAID1@ppc64le-hmc-4disk
https://openqa.suse.de/tests/11076768#step/bootloader_start/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.

Actions

Also available in: Atom PDF