Project

General

Profile

action #122176

[ppc64le][y] test fails in bootloader - waiting for lpar x to shutdown

Added by punkioudi 3 months ago. Updated 25 days ago.

Status:
New
Priority:
High
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-12-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

All ppc64le tests fail in the latest 15-SP5 runs with the message waiting for lpar 12 to shutdown

Observation

openQA test in scenario sle-15-SP5-Online-ppc64le-create_hdd_hmc_fips_envmode_Firefox@ppc64le-hmc-single-disk fails in
bootloader

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 61.1

Expected result

Last good: 58.1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#3 Updated by openqa_review 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: autoyast_create_hdd_gnome
https://openqa.suse.de/tests/10346206#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.

#4 Updated by okurz 2 months ago

  • Subject changed from [ppc64le] test fails in bootloader - waiting for lpar x to shutdown to [ppc64le][y] test fails in bootloader - waiting for lpar x to shutdown
  • Priority changed from Normal to High

punkioudi You created the ticket with the keyword [ppc64le] but not assigned to any team. This will make it likely that no one would pick up the ticket so I added [y] for the yam-team to look into.

#5 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: create_hdd_hmc_fips_envmode_Firefox
https://openqa.suse.de/tests/10435065#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.

#6 Updated by tjyrinki_suse about 1 month ago

  • Assignee set to szarate

Currently I think this particular problem about waiting for lpar x to shutdown is not shown, but it has been reported that the problems like https://openqa.suse.de/tests/10499341#step/bootloader/45 (public beta) or https://openqa.suse.de/tests/10375315#step/bootloader/38 (beta 3) are instead networking related problems (reading images in the bootloader).

Santiago asked to be assigned this ticket.

#7 Updated by openqa_review 25 days ago

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

This bug is still referenced in a failing openQA test: create_hdd_hmc_fips_envmode_Firefox
https://openqa.suse.de/tests/10576654#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.

Also available in: Atom PDF