Actions
action #159198
opencoordination #152771: [epic] Add migrations in maintenance
Simplify variables for VERSION and test modules for migrations in maintenance
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-04-18
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
Now we have added our first migration in maintenance updates is time to tackle problems mentioned in #157873 in a narrowed scope.
https://openqa.suse.de/tests/14054921
https://openqa.suse.de/tests/14054462
- We don't need to schedule
migration/version_switch_origin_system.pm
(looks like is resetting the console but that might not be needed either) when is scheduled for first time. autoyast/prepare_profile.pm
should run beforeautoyast/installation.pm
HDDVERSION
,ORIGIN_SYSTEM_VERSION
,UPGRADE_TARGET_VERSION
can be simplified to single openQA variableVERSION_2
(representing a secondary version, could be an origin one or a target one depending of the version of the job group running the job).- The second time
migration/version_switch_origin_system.pm
is scheduled we should replaced by a new module which exclusively will set the new version (and perhaps reset the console if needed), the rest of the code multi-architecture or including other setup will not be contained in this new module.
Acceptance criteria¶
AC1: Simplification in the use of settings and test modules for one openQA job running migration between two product is provided only in the scope of maintenance updates.
Updated by JERiveraMoya 13 days ago
- Subject changed from Merge vars HDDVERSION,FROM_VERSION and ORIGIN_SYSTEM_VERSION to Simplify variables for VERSION and test modules for migrations in maintenance
Updated by JERiveraMoya 7 days ago
- Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Updated by JERiveraMoya 1 day ago
- Status changed from Workable to New
Let's rethink this after merging https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19191/
Actions