action #118336
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Enhance code to make sure boot_to_desktop work for ppc64le
Description
Motivation¶
Sometimes on ppc64le it won't bonce back to bootloader and directly boot up, this cause test failed.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/f0fc149aa7872e911f415fc659f7a6c6ba28f841/lib/bootloader_setup.pm#L267
Not stable for the boot_to_desktop on ppc64le textmode, we need find the root cause and make it robust. The current code hasn't covered such situation that the bonce back never happened and boot up directly, so maybe we can think to improve code by add the operation for this scenario.
Ex:
https://openqa.nue.suse.com/tests/9715830#step/boot_to_desktop/11
https://openqa.nue.suse.com/tests/9715829#step/boot_to_desktop/7
Acceptance criteria¶
AC1: Add code to deal with the situation that the bonce back never happened and boot up directly.
Updated by JERiveraMoya over 1 year ago
- Tags deleted (
qe-yast-refinement)
unsupported virtualization, we should consider if this product works with PowerVM.
no need for checking tickets that I didn't move to refinement.
I will move to backlog to check later.
Updated by JERiveraMoya over 1 year ago
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
Looks feasible and I'm not sure about PowerVM for older products, so we can tackle it, thanks for checking it.
Updated by JERiveraMoya over 1 year ago
let's send some draft PR to see how we can help.
Updated by geor over 1 year ago
Updated by favogt over 1 year ago
Is this the same issue as https://progress.opensuse.org/issues/113447, i.e. caused by openQA slowness?
I can't check because the links to failed tests are broken meanwhile.
Updated by leli over 1 year ago
favogt wrote:
Is this the same issue as https://progress.opensuse.org/issues/113447, i.e. caused by openQA slowness?
I can't check because the links to failed tests are broken meanwhile.
I don't think they are the same issue, cause this issue is specific for ppc64le, while the issue you mentioned is for aarch64.
Updated by favogt over 1 year ago
leli wrote:
favogt wrote:
Is this the same issue as https://progress.opensuse.org/issues/113447, i.e. caused by openQA slowness?
I can't check because the links to failed tests are broken meanwhile.
I don't think they are the same issue, cause this issue is specific for ppc64le, while the issue you mentioned is for aarch64.
My argument is that the issue is not specific to any architecture.
Updated by coolgw over 1 year ago
There still some failed case after bounce back of ppc:
https://openqa.suse.de/tests/9889458#step/grub_test_snapshot/26 <== need adjust assert tag?
https://openqa.suse.de/tests/9889456#step/boot_to_desktop/9 <== need enlarge the timeout?
https://openqa.suse.de/tests/9889455#step/snapper_rollback/22 <== need enlarge timeout?
we should open another ticket for fix above failure or we continue fix it within this ticket? I just use this ticket to flag error in openqa currently
Updated by geor over 1 year ago
PR that addresses the first and second issue Wei mentioned: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15859
Updated by geor over 1 year ago
PR that addresses the thrid issue that Wei mentioned: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15873
Updated by openqa_review about 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles12sp4_ltss_media_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/10917229#step/boot_to_desktop/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 132 days if nothing changes in this ticket.
Updated by JERiveraMoya about 1 year ago
- Status changed from Feedback to Resolved
Updated by openqa_review 12 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: online_sle12sp5_sles15sp4_sles15sp5_pscc_all_full_y_
https://openqa.suse.de/tests/11022913#step/online_migration_setup/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.
Updated by openqa_review 10 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: online_sle12sp5_sles15sp4_sles15sp5_pscc_all_full_y_
https://openqa.suse.de/tests/11147138#step/online_migration_setup/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.