action #127655
closed
Continue migration sles15sp1_sles15sp4 failed on s390x, need to activate legacy and container modules
Added by hjluo about 1 year ago.
Updated 3 months ago.
Description
Motivation¶
- In build 90.1 in SLE-15-SP5-Continuous-Migration-SLE15SP5-s390x-90.1, the case offline_sles15sp1_sles15sp4_sles15sp5_media_all_full_s390x_ph0@s390x-kvm-sle12 failed during module upgrade_select, which need we to activate the legacy and container modules for s390x.
- But in the previous build, everything works without this error.
- We need to check what's wrong there.
Acceptance criteria¶
AC1: Check out the test to find out what's wrong with this test case for s390x.
AC2: Adapt the test settings if we need some changes here.
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Target version set to Current
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: offline_sles15sp1_sles15sp4_sles15sp5_media_all_full_
https://openqa.suse.de/tests/10943126#step/upgrade_select/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.
- Status changed from New to Rejected
Also available in: Atom
PDF