action #105049
open
[qe-core] System cannot boot after installation in s390x in multiple test suites
0%
Description
The following test suite are failing apparently for the same reason, not being able to boot after installation:
- https://openqa.suse.de/tests/7983462#step/handle_reboot/11
- https://openqa.suse.de/tests/7983463#step/handle_reboot/11
- https://openqa.suse.de/tests/7988913#step/validate_modify_existing_partition/2
- https://openqa.suse.de/tests/8089305#step/installation/26
There are retrieved logs at least in both of them.
In some other places, the test passes, like https://openqa.suse.de/tests/8089307.
Updated by 
Updated by
Updated by tjyrinki_suse over 1 year 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.
Updated by tjyrinki_suse over 1 year ago
- Related to action #98541: [qe-core][kernel] Steps in case of s390 failures added
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: 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:
- 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.
label:wontfix:boo1234
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: autoyast_reinstall
https://openqa.suse.de/tests/8375787
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.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by JERiveraMoya over 1 year ago
It keeps happening in multiple scenarios, Functional and YaST groups.