Project

General

Profile

Actions

action #137684

closed

coordination #130216: [epic] Adapt migration test coverage and its migration matrix for SLE 15 SP6

Cleanup migration test from SLE 15 SP3

Added by leli about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2023-10-10
Due date:
% Done:

0%

Estimated time:

Description

Motivation

After all tickets on optimizing migration from SLE 15 SP3 are resolved, we need to perform a final cleanup for those tests doing a migration from SLE 15 SP3.

ToDo

Iterate over all SLE 15 SP3 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.

If you can't match the test suite with an entry for SLE 15 SP3 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) 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

Acceptance criteria

AC1: Cleanup for migration from SLE 15 SP3 is done, all found issues fixed.
AC2: Ensure all new test suites with updated qcows.

Actions #1

Updated by leli about 1 year ago

  • Description updated (diff)
Actions #2

Updated by hjluo about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #3

Updated by hjluo about 1 year ago

MR 370

Actions #4

Updated by hjluo about 1 year ago

from Lemon:

I don't think it is a good time to review it, since there are 4 tickets 15SP3 related still open, we'd better wait and sync after these 4 tickets closed. So currently hang it for now, WDYT?

so now the MR was set to draft and wait there

Actions #5

Updated by hjluo about 1 year ago ยท Edited

now back to this ticket after all related tickets were done.

on 11/27/2023
Lemon Li
 I think all 15SP3 tickets resolved now, you can start the cleanup ticket. 
Shu Kui Liu
 I can provide some help, e.g. deleting the trailing whitespaces. (edited) 
Actions #6

Updated by leli about 1 year ago

Tina's comments on 15SP3:

Motivation
I reviewed milestone jobs group, found some jobs setting is not correct, need update
Update qcom image name:
offline_sles15sp3_rmt_basesys-srv-desk-dev-pcm_all_ful:
autoyast-SLES-15-SP3-s390x-GM-SDK-gnome-allpatterns.qcow2
offline_sles15sp3_rmt_basesys-srv-ltss-desk-nvidia_def_full:
SLES-15-SP3-aarch64-GM-ltss-desktop-nvidia-gnome-updated.qcow2" failed: 404 Not Found
online_sles15sp3_rmt_basesys-srv-desk-dev_all_full_zypp:
autoyast-SLES-15-SP3-s390x-GM-SDK-gnome-allpatterns.qcow2" failed: 404 Not Found
offline_sles12sp5_rmt_sdk-lp-asmm-contm-lgm-pcm-tcm-wsm_all_full:
SLES-12-SP5-s390x-GM-sdk-lp-asmm-contm-lgm-pcm-tcm-wsm-all_patterns-updated.qcow2
online_sles15sp3_scc_basesys-srv_389ds_server_all_full
autoyast-SLES-15-SP3-x86_64-textmode-updated.qcow2
rmt_import
SLES-15-SP5-x86_64-Build39.1@64bit-gnome.qcow2

For RMT and SMT test case:
Need update settings https -> http (As https has some problem now)

For 'online_sles15sp3_smt_basesys-srv-ltss_all_full_zdup' this jobs use wrong DESKTOP setting, its image use gnome, but DESKTOP setting is textmode, need check matrix to confirm which desktop should be used

Actions #7

Updated by tinawang123 about 1 year ago

Need update setting for 'https://openqa.suse.de/tests/12923925'
It lost original product version.

Actions #10

Updated by hjluo 12 months ago

2 MRs were merged.

Actions #11

Updated by zoecao 12 months ago

Please take a look at whether need to cleanup these two testsuites from milstone:
online_sles15sp3_scc_basesys-srv_389ds_server_all_full & online_sles15sp3_scc_basesys-srv_389ds_client_all_full

Actions #13

Updated by hjluo 12 months ago

zoecao wrote in #note-11:

Please take a look at whether need to cleanup these two testsuites from milstone:
online_sles15sp3_scc_basesys-srv_389ds_server_all_full & online_sles15sp3_scc_basesys-srv_389ds_client_all_full

Now Chenzi has moved these 2 cases to the dev group.

Actions #14

Updated by hjluo 12 months ago

hjluo wrote in #note-12:

MR: https://gitlab.suse.de/qe-yam/openqa-job-groups-migrations/-/merge_requests/407/
removed this MR cause we moved these 2 389ds cases to the dev group.

Actions #15

Updated by hjluo 12 months ago

  • Status changed from In Progress to Resolved

close this ticket as resolved.

Actions #16

Updated by openqa_review 11 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: online_sles15sp3_smt_basesys-srv-ltss_all_full_zdup
https://openqa.suse.de/tests/13076782#step/boot_to_desktop#1/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions

Also available in: Atom PDF