Service Pack Migration in SUSE Manager
Service Pack Migration means "migrating" a system from one Service Pack level to another.
For SLES 12 and above we support skipping a service pack. Supported migrations include:
- SLES 12 SP0 > SLES 12 SP2
- SLES 12 SP1 > SLES 12 SP2
For below SLES 12; we only support one step at a time, so it will not be possible to do a migration from e.g. SP1 to SP3. Supported migrations include these:
- SLES 11 SP 1 -> SLES 11 SP 2
- SLES 11 SP 2 -> SLES 11 SP 3
- SLE 10 SP 2 -> SLE 10 SP 3
- SUSE Manager Proxy 1.2 -> SUSE Manager Proxy 1.7
Note that the migration from SLE 10 SP 4 to SLES 11 SP 1 is unsupported, while addon products are generally supported. So you can migrate in one step e.g.:
- SLES 11 SP1 + HA Extension SP1 -> SLES 11 SP2 + HA Extension SP2
Further note that currently it is only possible to schedule migrations for single systems.
The SP-Migration feature can be found in the Web UI:
Systems -> (select a system) -> Software -> SP-Migration
Proxy: remove ext4dev-kmp-default
In order to successfully migrate a SUSE Manager Proxy from 1.2 to 1.7, it is necessary to remove the package 'ext4dev-kmp-default' before the migration is triggered (only if it is installed of course). Otherwise the migration will fail since there is no update candidate for this package available in SP2. This is how to remove the package using SUSE Manager:
- Select the proxy system and navigate to: Software -> Packages -> List/Remove
- Find 'ext4dev-kmp-default' in the list of removable packages
- Mark the checkbox, click 'Remove Packages' and confirm the package removal
Proxy: jabberd not running
After the migration of a SUSE Manager Proxy it might be the case that jabberd is not running and this message shows up in /var/log/messages:
"jabberd/sm: db: couldn't open storage db: Invalid argument"
Run the following commands to fix this issue:
rcjabberd stop rm -f /var/lib/jabberd/db/* rcjabberd start
SP1 to SP2 migration
ext4 was moved from the standard SLES channels to SLES11-Extra channel and this can cause the following message and failure when performing a migration from SP1 to SP2.
Problem: ext4dev-kmp-default-0_184.108.40.206_0.7-7.9.74.x86_64 requires kernel(default:vmlinux) = 9da14d07e63d3ebb, but this requirement cannot be provided
There are two choices to fix this problem:
- if the host is not using the ext4 filesystem, that it is safe to de-install the ext4dev-kmp-default package. Remove the package and try SP migration the again.
- if the ext4 filesystem is required, you need to clone the SLES11-Extra channel and add it during the migration.
Warning: The SLES11-Extra channel is the same for all SPs and may affect the SP migration.