action #116036: Add new migration offline x86_64 scenarios from SLE-15-SP4 in 'Migration' and 'Migration: Milestone' job groups - qe-yam - openSUSE Project Management Tool

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (dev)
QE tools team - backlog (ready issues)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (dev)
QE tools team - non-estimated (unblocked) issues (infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - SLO high forecast
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
QE Yam backlog
QE Yam blocked issues
QE Yam closed yesterday
QE Yam issues IN_PROGRESS
QE Yam new action tickets per day
QE Yam new actions
QE Yam prio high, no updates last 4 weeks
QE Yam prio low & normal, no update for 1 year
QE Yam recjected yesterday
QE Yam resolved yesterday
QE Yam workable actions
soft failure tickets in progress
softfailure tickets resolved
softfailure tickets workable
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #116036

closed

coordination #115322: [Epic] Update test coverage based on PRD for migration paths in SLE 15 SP5

Add new migration offline x86_64 scenarios from SLE-15-SP4 in 'Migration' and 'Migration: Milestone' job groups

Added by JERiveraMoya about 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

zoecao

Target version:

Current

Start date:

2022-08-31

Due date:

% Done:

Estimated time:

Description

Motivation¶

For new product SLE-15-SP5 we need to setup configuration for scenarios which migrate from SLE-15-SP4.
List of offline scenarios to add for x86_64:

SLES:

Similar to autoupgrade_sles15sp3_scc_basesys-srv_all_full_auto
G89
G93
G94
G95
G96
G99
G101

SLED (all will change to python3):

Similar to offline_sled15sp3_rmt_basesys-desk-we-python2_all_full but with default patterns.
G103
G104
G105
G106

Acceptance criteria¶

AC1: Setup offline x86_64 scenarios which migrate from SLE-15-SP4 in 'Migration' and 'Migration: Milestone' job groups
AC2: File proper bugs if you find any issues

Suggestions¶

Configuration should be very similar to SLE-15-SP3, only some scenarios are moved to 'Milestone' job group as we run more combination in this job group for newer products. Also we do variations adding all patterns.
Check migration matrix

History
Notes
Property changes

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Description updated (diff)

Actions

Copy link

Updated by zoecao about 2 years ago

JERiveraMoya wrote:

Motivation¶

For new product SLE-15-SP5 we need to setup configuration for scenarios which migrate from SLE-15-SP4.
List of offline scenarios to add for x86_64:

SLES:
Migration daily group:

G87: offline_sles15sp4_pscc_basesys-srv_def_full (similar to offline_sles15sp2_ltss_pscc_basesys-srv_def_full)
G94: offline_sles15sp4_media_basesys-srv-desk-we-python3_def_full (similar to [offline_sles15sp3_media_basesys-srv-desk-we-python2_all_full])
G99: offline_sles15sp4_media_basesys-srv-wsm-contm_all_full (similar to [offline_sles15sp3_media_basesys-srv-wsm-contm_def_full])
G101: offline_sles15sp4_pscc_basesys-srv-lgm-pcm_all_full (similar to [offline_sles15sp3_pscc_basesys-srv-lgm-pcm_def_full])

Migration Milestone group:

G89: offline_sles15sp4_scc_base_all_minimal (similar to offline_sles15sp3_pscc_base_all_minimal)
G93: offline_sles15sp4_media_basesys-srv-desk-dev_all_full (similar to [offline_sles15sp3_media_basesys-srv-desk-dev_def_full])
G95: offline_sles15sp4_scc_basesys-srv-desk-we-python3_all_full (similar to [offline_sles15sp3_scc_basesys-srv-desk-we-python2_def_full])
G96: offline_sles15sp4_rmt_basesys-srv-lp-tsm_def_full (similar to [offline_sles15sp3_rmt_basesys-srv-lp-tsm_all_full])

SLED (all will change to python3):

Update the SLED part here (I can not edit the ticket's description) :
For SLED, need to convert the SLED-15-SP3 to SLED-15-SP4 in the cases setting and cases name. (all will change to python3)
Migration daily group:

G105: Convert offline_sled15sp3_media_basesys-desk-we-dev-python2_all_full
G106: Convert offline_sled15sp3_pscc_basesys-desk-we-phub-python2_def_full Migration Milestone group:
G103: Convert offline_sled15sp3_rmt_basesys-desk-we-python2_all_full
G102: Convert offline_sled15sp3_scc_basesys-desk-we-python2_def_full

Acceptance criteria¶

AC1: Setup offline x86_64 scenarios which migrate from SLE-15-SP4 in 'Migration' and 'Migration: Milestone' job groups
AC2: File proper bugs if you find any issues

Suggestions¶

Configuration should be very similar to SLE-15-SP3, only some scenarios are moved to 'Milestone' job group as we run more combination in this job group for newer products. Also we do variations adding all patterns.
Check migration matrix