SLES 12 SP5 DMS migration for a BYOS instance via a proxy server fails

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

Environment

SUSE Linux Enterprise Server for SAP Applications 12 SP5

Situation

During the upgrade from SLES 12 SP5 to SLES 15 SP1 on an AWS BYOS instance via a proxy server, the SUSEConnect command fails.

distro_migration.log

...
Calling: ['chroot', '/system-root', 'SUSEConnect', '--list-extensions']
SUSEConnect error: Get "https://scc.suse.com/connect/systems/activations": read tcp xxx.xxx.xxx.xxx:49702->99.83.188.102:443: read: connection reset by peer
...

When using a proxy server, the SUSEConnect --list-extensions command completes successfully when run manually. However, during migration, the command fails when using the proxy server, whereas it succeeds when the proxy server is not used.

Resolution

You need to perform the following steps on the server before attempting the DMS.

# vi /etc/sle-migration-service.yml
preserve:
static:
- /etc/sysconfig/proxy

This will cause DMS to copy the file over after booting to the migration image so it will use the proxy.

Cause

When using a proxy server, the file "/etc/sysconfig/proxy" must be copied to the DMS environment so it will make use of the proxy.

Disclaimer

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.