action #165737
opencoordination #163316: [epic] Update migrations scenarios for SLE 15 SP7
Add migration testsuites for SLED15SP6 migration path to SLED15SP7
0%
Description
Motivation¶
Based on email: major changes in SLE 15 SP7 (when compared to SLE 15 SP6), there's a little change on SLED15 migration: for SLED 15, migration from the previous two SPs is supported (no change, but it was a bit cryptic in the PRD of 15 SP6).
So instead of updating the current SLED migration testsuites from SLED15SP5 to SLED15SP6 base, we need to keep the SLED15SP5 base testsuites and add new testsuites of SLED15SP6 base.
Reference the [15SP7 Migration Matrix], add migration testsuites for SLED15SP6 migration path to SLED15SP7.
- Reference the following sled15sp5 testsuites and adapt them to sled15sp6 (testsuite names and settings) and add to [support images group]
- supp_sled15sp5
- supp_sled15sp5_all
- Reference the following sled15sp5 migration testsuites and adapt them to sled15sp6 (testsuite names and settings), add them to [migration group]:
- migr_sled15sp5
- migr_sled15sp5_dev
- migr_sled15sp5_dev_all
- Reference the folloing sled15sp5 milestone testsuites and adapt them to sled15sp6 (testsuite names and settings), and add them to [migration milestone group]:
- migr_sled15sp5_phub
- migr_sled15sp5_dev
- migr_sled15sp5
- remove this testsuite from milestone group: migr_sled15sp5_desktop-we-phub-python3 which it not existing on matrix.
####Acceptance criteria
AC1 : Add support images for SLED15SP6 as above.
AC2 : Add migration testsuites for the scenarios listed above to migration group.
AC3 : Add migration milstone testsuites for the scenarios listed above to migration milestone group.
Updated by openqa_review about 2 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: migr_sled15sp5_dev
https://openqa.suse.de/tests/15354723#step/yast2_migration/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.
Updated by openqa_review about 1 month ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migr_sled15sp5_dev
https://openqa.suse.de/tests/15404813#step/yast2_migration/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.
Updated by openqa_review 11 days ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migr_sled15sp5_dev
https://openqa.suse.de/tests/15641163#step/yast2_migration/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 32 days if nothing changes in this ticket.
Updated by JERiveraMoya 8 days ago
- Tags set to qe-yam-oct-sprint
- Status changed from New to Workable
Updated by JERiveraMoya 4 days ago
- Tags changed from qe-yam-oct-sprint to qe-yam-nov-sprint