action #137846
Updated by leli 7 months ago
#### Motivation
After all tickets on optimizing migration from SLE 15 SP4 are resolved, we need to perform a final cleanup for those tests doing a migration from SLE 15 SP4.
#### ToDo
Iterate over all SLE 15 SP4 related testsuites in the jobgroups mentioned under "Scope" and check if you can find a matching entry for that testsutie in the spreadsheet named `draft_redesign_matrix"`in the [test matrix document](https://mysuse-my.sharepoint.com/:x:/r/personal/chcao_suse_com/_layouts/15/doc2.aspx?sourcedoc=%7B0278E2B7-01AD-4E4F-B78F-00B05A53242F%7D&file=draft_sle15sp6-migration-matrix-20230602.ods&action=default&mobileredirect=true&cid=cd782e0a-f8ea-4e18-8070-0f5322c6d9fc).
If you can't match the test suite with an entry for SLE 15 SP4 in the `draft_redesign_matrix` then
* verify whether if something is wrong for test suite name and setting and then update it
* verify if it is an unexpected old test suite then remove it
For testsuite that match the `draft_redesign_matrix` check if the testsuite is consistent.
Example for unexpected base test:
~~~
- offline_sles12sp5_pscc_def:
testsuite: offline_sles12sp5_pscc_sdk_full
~~~
In this example the testsuite `offline_sles12sp5_pscc_def` uses a stored testsuite (from [openQA admin menu](https://openqa.oqa.prg2.suse.org/admin/test_suites)) named `offline_sles12sp5_pscc_sdk_full` that uses the `sdk` addon which is not required for `offline_sles12sp5_pscc_def`.
If such a consistency issue is found then
* copy the **needed** testsuite settings form the openQA admin page to the job group YAML file.
* use `testsuite: null` instead of the wrong `testsuite` reference.
#### Scope
* Migration daily job group: (https://openqa.nue.suse.com/group_overview/265)
* Migration milestone job group: (https://openqa.nue.suse.com/group_overview/266)
#### Acceptance criteria
**AC1**: Cleanup for migration from SLE 15 SP4 is done, all found issues fixed.
**AC2**: Ensure all new test suites with updated qcows.
Back