Proxy Migration from 5.1 to 5.2

1. Verify System and SUSE Multi-Linux Manager Tools version.

   cat /etc/os-release
   mgrpxy --version

   Confirm:

   • Operating System: SL Micro 6.1

   • Tools version: mgrpxy version 5.1.x or higher

2. Check running containers.

   podman ps

   Ensure the following containers are running:

   • proxy-squid

   • proxy-ssh

   • proxy-httpd

   • proxy-tftpd

   • proxy-salt-broker

3. Synchronize the new Proxy Products in SUSE Multi-Linux Manager Server. For more information, see Software Products.

   Use the Web UI to synchronize:

   • SL Micro 6.2

   • SUSE Multi-Linux Manager Proxy Extension 5.2 Beta 1

4. Perform proxy product migration. For more information, see Product Migration.

   Navigate to the proxy system and select Systems  Overview > Software  Product Migration.

   Migrate from

   • SL Micro 6.1 + SUSE Multi-Linux Manager Proxy 5.1 Extension

     to

   • SL Micro 6.2 + SUSE Multi-Linux Manager Proxy Extension 5.2 Beta 1

     Do not select optional channels when prompted, unless you have confirmed they are required.

     It is recommended to do a dry-run first before performing the actual migration.

5. Monitor the migration action.

   You can follow the process under Systems  Details  Events tab in the Web UI.

6. After the upgrade completes, stop the proxy container and then reboot the system.

   mgrpxy stop
   reboot

7. Perform post-reboot checks.

   Verify upgraded OS and SUSE Multi-Linux Manager extension:

   cat /etc/os-release
   SUSEConnect --status-text

8. Verify SUSE Multi-Linux Manager tools version.

   mgrpxy --version

   Expected output:

   • mgrpxy version 5.2.0 or higher

9. Install the new proxy container images as RPM packages if they are not pulled from the registry.

   transactional-update pkg install suse-multi-linux-manager-5.2-<arch>-proxy*

10. Reboot the Proxy.

11. Upgrade proxy containers and restart them.

    mgrpxy upgrade podman
    mgrpxy stop
    mgrpxy start

12. Confirm proxy containers are operational.

    podman ps

    All expected proxy containers should be up and running:

    • proxy-salt-broker

    • proxy-httpd

    • proxy-squid

    • proxy-tftpd

    • proxy-ssh

1. Verify operating system and SUSE Multi-Linux Manager tools version.

   cat /etc/os-release
   mgrpxy --version

   Confirm:

   • Operating System: SUSE Linux Enterprise Server 15 SP7

   • Tools version: mgrpxy version 5.1.x or higher

2. List running proxy containers.

   podman ps

   Ensure the following containers are running:

   • proxy-salt-broker

   • proxy-httpd

   • proxy-squid

   • proxy-tftpd

   • proxy-ssh

3. Synchronize the new Products in SUSE Multi-Linux Manager Server using the Web UI.

   For more information, see Software Products.

   Synchronize:

   • SUSE Multi-Linux Manager Proxy Extension 5.2 Beta 1

4. Perform proxy product migration.

   For more information, see Product Migration.

   Navigate to the proxy system and select Systems  Overview > Software  Product Migration.

   Migrate from:

   • SUSE Linux Enterprise Server 15 SP7 + SUSE Multi-Linux Manager Proxy 5.1 Extension

     to:

   • SUSE Linux Enterprise Server 15 SP7 + SUSE Multi-Linux Manager Proxy Extension 5.2 Beta 1

     Do not select optional channels when prompted, unless you have confirmed they are required.

     It is recommended to do a dry-run first before performing the actual migration.

5. Monitor the migration action.

   You can follow the process under Systems  Details  Events in the Web UI.

6. After the upgrade completes, stop the proxy container and then reboot the system.

   mgrpxy stop
   reboot

7. Perform post-reboot checks.

   Verify the OS and SUSE Multi-Linux Manager extension version:

   cat /etc/os-release
   SUSEConnect --status-text

8. Verify SUSE Multi-Linux Manager tools version.

   mgrpxy --version

   Expected output:

   • mgrpxy version 5.2.0 or higher

9. Install the new proxy container images as RPM packages if they are not pulled from the registry.

   zypper install suse-multi-linux-manager-5.2-<arch>-proxy*

10. Reboot the Proxy.

11. Upgrade proxy containers and restart them.

    mgrpxy upgrade podman
    mgrpxy stop
    mgrpxy start

12. Confirm proxy containers are operational.

    podman ps

    All expected proxy containers should be up and running:

    • proxy-salt-broker

    • proxy-httpd

    • proxy-squid

    • proxy-tftpd

    • proxy-ssh