action #135575
Updated by rainerkoenig 8 months ago
#### Motivation After Following the new [test matrix](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), after all tickets on optimizing migration from SLE12-SP5 in #130216 are resolved, optimize work done for SLE12-SP5, we need to perform a final cleanup for those tests doing a the migration test from SLE 12 SP5. SLE12-SP5. #### ToDo Iterate over all SLE 12 SP5 related testsuites in The idea is to compare with the jobgroups mentioned under "Scope" and check test matrix, 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 SLE12 SP5 in the `draft_redesign_matrix` then * not matched, verify whether if something is wrong for test suite name and setting and setting, if yes then update it * verify it, if it is an a unexpected old test suite then remove it For testsuite that match it. Besides, take care whether something wrong in the `draft_redesign_matrix` check if the testsuite is consistent. Example for unexpected test suite. Ex: Unexpected base test: test ~~~ - offline_sles12sp5_pscc_def: testsuite: offline_sles12sp5_pscc_sdk_full ~~~ In this example This will cause 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` test suite of offline_sles12sp5_pscc_def with unexpected addon which is not required for `offline_sles12sp5_pscc_def`. of 'sdk'. If such a consistency issue We don't suggest to continue use old test suite (https://openqa.oqa.prg2.suse.org/admin/test_suites) in yaml template, so it is found then * copy the **needed** testsuite settings form the openQA admin page better to the job group YAML file. * use `testsuite: null` instead of the wrong `testsuite` reference. move such old test suite to yaml template instead. #### Scope * Migration daily job group: (https://openqa.nue.suse.com/group_overview/265) group(https://openqa.nue.suse.com/group_overview/265) * Migration milestone job group: (https://openqa.nue.suse.com/group_overview/266) group(https://openqa.nue.suse.com/group_overview/266): #### Acceptance criteria **AC1**: Cleanup for migration from SLE12-SP5 is done, all found issues fixed. SLE12-SP5.