Product Migration

Table of Contents

1. Product Mass Migration

Product migration allows you to upgrade SLE-based client systems from an Service Pack (SP) level to a later one. For example, you can migrate SUSE Linux Enterprise 15 SP1 to SUSE Linux Enterprise 15 SP2.

You can also migrate openSUSE Leap to a later minor version or to the corresponding SLE SP level, for example:

openSUSE Leap 15.1 to 15.2, or
openSUSE Leap 15.1 to SUSE Linux Enterprise 15 SP1, or
openSUSE Leap 15.2 to SUSE Linux Enterprise 15 SP2

During migration, Uyuni automatically accepts any required licenses (EULAs) before installation.

In SUSE Linux Enterprise 12 and later, SUSE supports service pack skipping if SUSE Customer Center provides it. For example, you can upgrade from SUSE Linux Enterprise 15 to SP2, without installing SP1. For supported SUSE Linux Enterprise upgrade paths, see https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-upgrade-paths.html#sec-upgrade-paths-supported.

Product migration is for upgrading within the same major version. You cannot use product migration to migrate from SUSE Linux Enterprise 12 to SUSE Linux Enterprise 15. For more information about major upgrades, see client-configuration:client-upgrades-major.adoc.

Product migration does not have a rollback feature. When the migration procedure has begun, rolling back is not possible. Ensure you have a working system backup available, in case of an emergency.

Before starting the product migration, ensure there are no pending updates or patches. Check the System Status on the client system’s Details Overview page, and install all offered updates or patches. If your client system is not uptodate, product migration may fail.

Before starting a migration, make sure all the channels of the target product are fully synchronized. To check the synchronization status in the Web UI, navigate to the Admin Setup Wizard Products page.

Procedure: Performing a Migration

From the Systems Overview page, select a client.
From the system details page of the client, navigate to the Software Product Migration tab.
Select the target migration path and click Select Channels.
From the Product Migration - Channels page select the correct base channel, including Mandatory Child Channels and any additional Optional Child Channels.
OPTIONAL: Check Allow Vendor Change to allow packages that have changed vendors to be installed. If this occurs, a notification is shown with details before the migration is started.

To migrate openSUSE Leap to SUSE Linux Enterprise, you must check the Allow Vendor Change option.
Click Schedule Migration when your channels have been configured properly.

1. Product Mass Migration

If you want to migrate a large number of clients to the next SP version, you can use Uyuni API calls.

Procedure: Performing a Product Mass Migration

List available migration targets, and take note of the system IDs you want to migrate:
```
spacecmd api -- system.listMigrationTargets -A 1000010001
```
For each system ID, call listMigrationTarget and check that the desired target product is available.
- If the system ID has an available target, call system.scheduleProductMigration.
- If the desired target is not available, skip the system.

Adapt this template for your environment:

target = '[....]'
basechannel = 'channel-label'
system_ids = [1, 2, 3]

session = auth.login(user, pass)
for system in system_ids
  if system.listMigrationTargets(session, system).ident == target
    system.scheduleProductMigration(session, system, target, basechannel, [], False, <now>)
  else
    print "Cannot migrate to requested target -- skipping system"
  endif
endfor