action #121021
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
upgrade_snapshots fails in post_run_hook due to no prompt
Added by hjluo over 1 year ago.
Updated about 1 year ago.
Description
Motivation¶
openQA test in scenario sle-15-SP5-Regression-on-Migration-from-SLE12-SPx-ppc64le-offline_sles12sp5_media_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g fails in
upgrade_snapshots
Looks like we timout in the post_run_hook in consoletest.pm, but actually the last command, the wait_serial in upgrade_snapshots.pm succeeds, but the last command doesn lead us to a correct prompt so it cannot run the post_run_hook properly.
See correct prompt here in last succesfull: https://openqa.suse.de/tests/10481195#step/upgrade_snapshots/7
Acceptance criteria¶
AC1: Try to get the prompt to be able to run the post_run_hook
Additional information¶
As there are little chances that bugs open for Power KVM would be solved we should find some simple solution, like disable part of this scenario or completely in case of not finding a good solution.
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles12sp5_media_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/10092057#step/upgrade_snapshots/1
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 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles12sp5_media_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/10500564#step/upgrade_snapshots/1
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.
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Subject changed from timeout in in upgrade_snapshots to upgrade_snapshots fails in post_run_hook
- Description updated (diff)
- Subject changed from upgrade_snapshots fails in post_run_hook to upgrade_snapshots fails in post_run_hook due to no prompt
- Description updated (diff)
- Parent task set to #121876
- Description updated (diff)
- Status changed from Workable to In Progress
- Assignee set to JRivrain
Looking at this, I would completely disable this test suite or migrate it to Powervm: in last build 7 test modules are failing due to system being apparently extremely irresponsive. It probably does not make sense fixing this, we already have TIMEOUT_SCALE=2 and trivial commands don't even get typed.
The problem seems to be a kernel failure but we can't report it as the backend is not supported...
- Status changed from In Progress to Resolved
The test causes an OOM situation. It is a bug, but this backend is no longer supported. Adding memory allows other modules to pass, but is resource consuming, and the test module itself is still failing anyway. I tested the same commands on a powervm machine, the bug was not appearing there. Un-scheduling this module will allow the other test modules to pass.
PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16537
Also available in: Atom
PDF