Proxy Migration

In SUSE Manager 4.3, the proxy can be deployed using three different methods: RPM based, containerized running on podman or k3s.

In SUSE Manager 5.0.1, management of the containerized proxy running with podman was re-designed and made simpler with the mgrpxy tool. At the same time, RPM based support was removed, and only the containerized version running with podman or k3s is supported.

This section describes migrating from Proxy 4.3 using the mgrpxy tool.

An in-place migration from SUSE Manager 4.3 to 5.0 is unsupported due to the HostOS change from SUSE Linux Enterprise Server 15 SP4 to SLE Micro 5.5.

The traditional contact protocol is no longer supported in SUSE Manager 5.0 and later. Before migrating from SUSE Manager 4.3 to 5.0.1, any existing traditional clients including the traditional proxies must be migrated to Salt.

For more information about migrating traditional SUSE Manager 4.3 clients to Salt clients, see https://documentation.suse.com/suma/4.3/en/suse-manager/client-configuration/contact-methods-migrate-traditional.html

1. Deploy a New SUSE Manager Proxy

Because in-place migration is not supported, the users must deploy a new SUSE Manager proxy with a new FQDN.

2. Migrate Clients to the New Proxy

Before migrating the clients, ensure that the new proxy is already deployed and fully functional.
Procedure: Migrating Client between Proxies

  1. Log in to the SUSE Manager Server Web UI.

  2. From the left navigation, select Systems  Systems List.

  3. Navigate to the old 4.3 proxy page, and click the Proxy tab.

  4. Select all system to "SSM".

  5. From the left navigation, select Systems  System Set Manager.

  6. Select the sub-menu Misc  Proxy.

  7. From the drop down select the new proxy to migrate to.

  8. Click on Change Proxy.

  9. After this action, minions will be migrated to the new proxy.

  10. You can check the schedule progress to verify if all systems were successfully migrated.

After a few minutes, the machines will start to show up the new connection path. When all machines have the connection path under the new proxy, the old 4.3 proxy machine is not needed anymore and can be removed.