Project

General

Profile

Actions

action #109067

closed

[sle][migration][sle15sp4] - TechPreview: yast-migration-sle a simplified Leap -> SLE migration

Added by hjluo about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
-
Start date:
2022-03-28
Due date:
% Done:

100%

Estimated time:
20.00 h
Difficulty:

Description

https://jira.suse.com/browse/SLE-24226
Yast team has developed a simplified migration tool for Leap called yast-migration-sle.

https://build.opensuse.org/package/show/YaST:Head/yast2-migration-sle

We should also update https://en.opensuse.org/SDB:How_to_migrate_to_SLE with the instructions for the new setup.

We would like to mention it as tech preview in release notes and existing SLE documentation https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-upgrade-online.html#sec-upgrade-online-leap-to-sle

Actions #1

Updated by leli about 2 years ago

  • Category set to New test
  • Estimated time set to 20.00 h
Actions #2

Updated by hjluo almost 2 years ago

./hj-tools/hj-branch.sh -a hjluo -b suseconnect-ng -j 8419963 -s "_GROUP=0 LEAP_TECH_PREVIEW=1"
https://openqa.nue.suse.com/t8429262

Actions #3

Updated by hjluo almost 2 years ago

https://github.com/yast/yast-migration-sle

Description
This YaST module allows online migration from the openSUSE Leap distribution to the SUSE Linux Enterprise (SLE) product. The migration is done in a live running system.

It uses the yast2-registration and yast2-migration modules as the backend. That means it provides the very same functionality which can be done using these two modules but in a simplified way.

For migrating to SLES you need a SLES registration key, see https://www.suse.com/support/ how to obtain it. You can create a 60-day trial activation code at https://www.suse.com/download/sles/ (you need to have a SUSE account for that).

Features
Simplified workflow for migrating openSUSE Leap installations to SUSE Linux Enterprise (SLE) product
Can register against SUSE Customer Service (SCC) server or any local RMT or SMT server
Supports rollback when the migration fails or is aborted
Because openSUSE Leap shares many packages with SLE the migration should usually install just few packages, it should not completely reinstall the system
Workflow
Online update check - at the beginning the module checks whether there is an update for software stack and asks to install it. This should ensure the package installation later works fine. If an update for this module is needed it should be marked as a software stack update as well.
Entering the registration data - the module asks for the e-mail address and the SLE registration code, alternatively you can enter the address of the local RMT/SMT server (email and registration code are not required in that case)
Registration - the system is registered to the registration server and the openSUSE Leap repositories from the server are added into the system
Selecting a migration - if only one migration to a SLE product is available then it is automatically selected, if there are multiple migrations a selection dialog is displayed and the user needs to select the migration manually
Migration - the registration is then migrated to the selected SLE product and the Leap repositories are changed to the SLE repositories
License agreement - displays the SLE product license and requires accepting it, if the license is not accepted the migration is aborted (see the rollback section below)
Migration summary - the dialog displays the summary about the installed or upgraded products and packages, if there is a package dependency problem then it needs to be manually resolved before continuing
Package installation - the SLE packages are installed into the system, this can take some time
Congratulation - a congratulation dialog is displayed to confirm a successful migration
Reboot - it is recommended to manually reboot the system to ensure all changes take effect
Rollback
When the migration fails or is aborted then YaST restores the original repositories in the system and moves the registration from SLE back to openSUSE Leap. However, the system still remains in a registered state.

If you want to fully unregister the system then run this command as root:

SUSEConnect --de-register

Actions #4

Updated by hjluo almost 2 years ago

added 3 new cases:

  • online_leap15.4_scc_textmode_def_full_tech_y:
  • online_leap15.4_scc_gnome_def_full_tech_y:
  • online_leap15.4_scc_kde_def_full_tech_y:
Actions #5

Updated by hjluo almost 2 years ago

./hj-tools/hj-branch.sh -a hjluo -b leap_tech -j 8419963 -s "_GROUP=0 LEAP_TECH_PREVIEW=1 LEAP_TECH_PREVIEW_REPO=https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.4/YaST:Head.repo"

https://openqa.nue.suse.com/t8434742

Actions #6

Updated by hjluo almost 2 years ago

wait Lubo announce us in the coming build

Actions #8

Updated by hjluo almost 2 years ago

./hj-tools/hj-branch.sh -a hjluo -b leap_tech -j 8625914 -s "_GROUP=0 LEAP_TECH_PREVIEW=1 LEAP_TECH_PREVIEW_REPO=https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.4/YaST:Head.repo"
https://openqa.nue.suse.com/t8627926

for i in 8625913 8625912 8625914; do
https://openqa.nue.suse.com/t8627928
https://openqa.nue.suse.com/t8627929
https://openqa.nue.suse.com/t8627930

Actions #9

Updated by hjluo almost 2 years ago

for i in 8625913 8625912 8625914; do
./hj-tools/hj-branch.sh -a hjluo -b leap_tech -j $i -s "_GROUP=0 LEAP_TECH_PREVIEW_REPO=https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.4/YaST:Head.repo"

done
https://openqa.nue.suse.com/t8638142
https://openqa.nue.suse.com/t8638143
https://openqa.nue.suse.com/t8638144

Actions #10

Updated by hjluo almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 40 to 100

PR merged

Actions

Also available in: Atom PDF