DMS (Distribution Migration System) Migration failed

This document (000020634) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12


The Distribution Migration System provides an upgrade path for an installed SUSE Linux Enterprise system or SUSE Linux Enterprise Server for SAP Applications from one major version to another. For example, from SUSE Linux Enterprise Server 12 SP5 to SUSE Linux Enterprise Server 15 SP3.

zypper multiple kernel feature

One possible cause of migration failure is due to the zypper multiple kernel feature being enabled, which leaves multiple kernels on the system. Normally this is correct and acceptable, however, due to a kernel RPM script change in certain kernel packages, this is causing a conflict and the older kernels are unable to be removed. 

The DMS procedure may fail completely or partially, depending on where in the process the old/previous kernel is removed.

Look in the log "/var/log/distro_migration.log" for "Migration failed".

These types of errors are seen when the kernel is being removed:
( 928/1204) Removing kernel-default-4.12.14-122.106.1.x86_64 [....error]
Removal of (24555)kernel-default-4.12.14-122.106.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.VECCEi: line 1: /usr/lib/module-init-tools/kernel-scriptlets/rpm-preun: No such file or directory
error: %preun(kernel-default-4.12.14-122.106.1.x86_64) scriptlet failed, exit status 127
error: kernel-default-4.12.14-122.106.1.x86_64: erase failed

Abort, retry, ignore? [a/r/i] (a): a
Warning: %posttrans scripts skipped while aborting:

Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.

Migration failed.

The migration to the new service pack has failed. The system is most
likely in an inconsistent state.

This may leave the system not migrated at all, or only partially migrated.

If most updates are installed, then a simple "zypper update" after a reboot should finalize the migration.

Incorrect product defined in /etc/sle-migration-service.yml

If for example the base product is SLES_SAP but one defined SLES in /etc/sle-migration-service.yml, for example this way:
migration_product: 'SLES/15.3/x86_64'

the migration will fail and one can see similar output in /var/log/distro_migration.log:
Calling: ['chroot', '/system-root', 'SUSEConnect', '--list-extensions']
command 'zypper --disable-repositories --xmlout --non-interactive products -i' failed
Error: zypper returned (7) with '<?xml version='1.0'?>
<message type="error">System management is locked by the application with pid 1781 (zypper).

SUSEConnect timeout

SUSEConnect failed to connect to
Calling: ['mount', '--bind', '/system-root/usr/lib/zypp/plugins/services', '/usr/lib/zypp/plugins/services']
Calling: ['chroot', '/system-root', 'SUSEConnect', '--list-extensions']
SUSEConnect error: Errno::ETIMEDOUT: Connection timed out - connect(2) for "" port 443


zypper multiple kernel feature

Engineering is aware of this situation and is investigating a resolution.

Until then the workaround is to manually remove extra RPMs before starting the DMS migration.

If the system is still showing as SLES12-SP5, then all kernel RPMs except the current running kernel will need to be removed prior to running the DMS procedure again.

To do that, check for current installed kernels:
rpm -qa|grep kernel-default

Check the current running kernel:
uname -r

Then remove any kernels that are older.

Here is an example:
rpm -qa|grep kernel-default
uname -r

The old kernel version is "kernel-default-4.12.14-122.83.1.x86_64".

Remove the old kernel:
zypper rm kernel-default-4.12.14-122.83.1

If in doubt, contact SUSE Support for further assistance.

Incorrect product defined in /etc/sle-migration-service.yml

Correcting the migration product should make the migration work as expected.

SUSEConnect timeout

The solution could vary depending on cause, but a known issue related to customer need to use HTTP proxy to connect to the internet.

Engineering is aware of incomplete handling of /etc/sysconfig/proxy inside DMS environment. The workaround is to create a shell wrapper for /usr/sbin/SUSEConnect which would explicitly define http_proxy environment variables later passed to original SUSEConnect script.



zypper multiple kernel feature

Due to a kernel RPM script change in certain kernel packages, this is causing a conflict and the older kernels are unable to be removed.


Incorrect product defined in /etc/sle-migration-service.yml

It is a misconfiguration since by default no 'migration_product' is set, and the migration will use that product as found in '/etc/products.d/baseproduct'.

SUSEConnect timeout

As for proxy related issue, since SUSEConnect is called from a script started via a systemd unit, no shell proxy related environment values are available by default because the systemd unit does not use 'EnvironmentFile=-/etc/sysconfig/proxy' setting.

Additional Information


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000020634
  • Creation Date: 02-May-2022
  • Modified Date:03-May-2022
    • SUSE Linux Enterprise Server
    • SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center