Project

General

Profile

Actions

action #105049

open

[qe-core] System cannot boot after installation in s390x in multiple test suites

Added by JERiveraMoya almost 3 years ago. Updated 9 months ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

The following test suite are failing apparently for the same reason, not being able to boot after installation:

There are retrieved logs at least in both of them.

In some other places, the test passes, like https://openqa.suse.de/tests/8089307.


Related issues 1 (0 open1 closed)

Related to openQA Tests (public) - action #98541: [qe-core][kernel] Steps in case of s390 failuresResolved2021-09-13

Actions
Actions #1

Updated by JERiveraMoya almost 3 years ago

  • Description updated (diff)
Actions #2

Updated by okurz almost 3 years ago

  • Category set to Bugs in existing tests
Actions #3

Updated by JRivrain almost 3 years ago

  • Description updated (diff)
Actions #5

Updated by tjyrinki_suse almost 3 years ago

  • Status changed from New to Workable
  • Assignee set to szarate
  • Start date deleted (2022-01-19)

Santiago has looked into this according to a discussion, but definition of "Workable" may depend on how one can think of a way to get to the root of the problem.

Actions #6

Updated by tjyrinki_suse almost 3 years ago

  • Related to action #98541: [qe-core][kernel] Steps in case of s390 failures added
Actions #7

Updated by openqa_review almost 3 years ago

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

This bug is still referenced in a failing openQA test: select_modules_and_patterns+registration@s390x-zVM-vswitch-l2
https://openqa.suse.de/tests/8206504

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
Actions #8

Updated by openqa_review over 2 years 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_reinstall
https://openqa.suse.de/tests/8375787

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 #9

Updated by JERiveraMoya over 2 years ago

It keeps happening in multiple scenarios, Functional and YaST groups.

Actions #10

Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF