action #132707
closed
coordination #130216: [epic] Adapt migration test coverage and its migration matrix for SLE 15 SP6
Create support images with module combinations and all patterns on SLE 12 SP5
Added by leli over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
Following the updated test matrix (see draft redesign matrix), we need to create support images with module combinations and all patterns on SLES 12 SP5.
The steps:
- Follow the test matrix to get the needed qcow list (for this ticket the row with for all patterns)
- boot the base+all patterns image, register the system again with the corresponding combination and patched, then de-register system before publishing qcow. (we do it in this way to avoid handling too many autoyast profiles and its maintenance.)
Note: minimal qcow excluded from this ticket, it was already done in other ticket.
Acceptance criteria¶
AC1: Create support images with module combinations and all patterns on SLE 12 SP5.
AC2: Create/modify configuration for running corresponding migrations
Additional info¶
About the test name and qcow name please follow the name document
test matrix
- Target version set to Current
- Parent task set to #132653
- Status changed from New to Workable
- Parent task changed from #132653 to #130216
- Related to action #132650: Create support image via autoyast with default patterns on SLE 12 SP5 added
- Related to action #132653: Create support image via autoyast with all patterns on SLE 12 SP5 added
- Related to deleted (action #132650: Create support image via autoyast with default patterns on SLE 12 SP5)
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to rfan1
- Status changed from In Progress 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_sles12sp5_media_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full
https://openqa.suse.de/tests/12120753#step/force_scheduled_tasks/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 Feedback to Resolved
Also available in: Atom
PDF