action #120543
closed
coordination #120534: [epic] Provide auto-installation test suites for supporting testing
Create a daily auto-installation for SLE 12 SP5 aarch64 (SDK + all patterns)
Added by JERiveraMoya over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
For Regression job group we need to replace the use of this image SLES-12-SP5-aarch64-GM-SDK-allpatterns.qcow2 in https://openqa.suse.de/tests/9919648
This installation use module SDK and install all patterns.
Acceptance criteria¶
AC1: Auto-installation for SLE 12 SP5 aarch64 (with SDK and all patterns) runs in YaST Maintenance Updates - Development
AC2: Use for example prefix sle_autoyast_* to distinguish it from ha, sap and other quarantined test suites
AC3: Configure jobs using that existing qcow2 to use the new fresh daily image
Additional information¶
Search for test suites using that image in all the Migration job groups.
As a first step to improve the situation with https://bugzilla.suse.com/show_bug.cgi?id=1204887 we should try to use auto-installation.
If this doesn't work we might need a follow-up to further dissect the problem, but it might be that the resolve issue will be gone with a new image and the bug might be consider invalid.
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Workable
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: online_sles15sp4_rmt_basesys-srv-lgm-pcm_all_full_zypp_pre
https://openqa.suse.de/tests/9960111#step/select_patterns/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 Workable to In Progress
Create a new qcow maybe fix this issue, while I still think if we want to fix the unexpected pattern issue, we'd better to find the root cause firstly(Add debug info in install pattern code and re-run the job).
Anyway, a new job created to create the new auto-installation qcow. https://openqa.nue.suse.com/tests/10111772#live
leli wrote:
Create a new qcow maybe fix this issue, while I still think if we want to fix the unexpected pattern issue, we'd better to find the root cause firstly(Add debug info in install pattern code and re-run the job).
Anyway, a new job created to create the new auto-installation qcow. https://openqa.nue.suse.com/tests/10111772#live
That is my point that we should not focus on patching system but in migrating them. Some errors might have very low probability to be faced by client unless they are testing with images created years ago! like we do... that is some kind of testing, but more of the kind of the corner case that the normal case. Let's see how it goes with a fresh system.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: online_sles15sp4_rmt_basesys-srv-lgm-pcm_all_full_zypp_pre
https://openqa.suse.de/tests/10164489#step/select_patterns/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 In Progress to Resolved
Also available in: Atom
PDF