Project

General

Profile

Actions

action #115991

closed

coordination #113644: [Epic] Add migration paths with unreleased maintenance updates

Setup in development group an offline migration SLE-15-SP3->SLE-15-SP4 with SLE-15-SP4 unreleased MUs

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

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-08-30
Due date:
% Done:

100%

Estimated time:

Description

Motivation

After attempting #113647 we should try the other half of the way and create automation for migration from SLE-15-SP3 to SLE-15-SP4 with unreleased maintenance updates of SLE-15-SP4 (in previous tickets we use unreleased maintenance updates from SLE-15-SP3).
Basically we will be using exacting the same test to cover the other part.

Acceptance criteria

AC1: Setup in development group (with control version) new test suite to perform this migration
AC2: Migration adding unreleased maintenance updates runs successfully or it is label with corresponding filed bug.

Suggestions

Test suite autoupgrade_sles15sp3_scc_basesys-srv_all_full_auto was used as base for previous work.
AutoYaST profile autoyast_scc_up.xml should be used as base for a new AutoYaST profile which should include functionality for adding the unreleased maintenance repos, for that please check:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/autoyast_sle15/create_hdd/create_hdd_maintenance.xml.ep#L33
used for example here: https://openqa.suse.de/tests/9460584#step/installation/3

Actions

Also available in: Atom PDF