Proxy Upgrade from 5.0 to 5.2

1. Verify System and Uyuni Tools version.

   cat /etc/os-release
   mgrpxy --version

   Confirm:

   • Operating System: SLE Micro 5.5

   • Tools version: mgrpxy version 0.1.29 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 Uyuni Server. For more information, see Software Products.

   Use the Web UI to synchronize:

   • SL Micro 6.2

   • Uyuni Proxy Extension 2026.06

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

   • SLE Micro 5.5 + SUSE Manager Proxy 5.0 Extension

     to

   • SL Micro 6.2 + Uyuni Proxy Extension 2026.06

     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.

   reboot
   mgrpxy stop

7. Perform post-reboot checks.

   Verify upgraded OS and Uyuni extension:

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

8. Verify Uyuni tools version.

   mgrpxy --version

   Expected output:

   • mgrpxy version 5.2 or higher

9. Enable Root SSH Access (if required). SL Micro 6.2 disables root login via SSH by default. Edit /etc/ssh/sshd_config.d/sshd.conf:

   PermitRootLogin yes

   Restart the service:

   systemctl restart sshd

   For more information, see Remote root login on SL Micro.

10. Install the new proxy container images as RPM packages.

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

11. Reboot the Proxy.

12. Upgrade proxy containers and restart them.

    mgrpxy upgrade podman
    mgrpxy stop
    mgrpxy start

    For air-gapped installations, first upgrade the container RPM packages, then run the mgrpxy upgrade podman command.

    Or, those running on a Kubernetes cluster can update using:

    mgrpxy upgrade kubernetes

13. Clean up the unused container images to free disk space:

    podman image prune -a

    In some upgrades, multiple *.rpmnew and *.rpmsave files may be generated. The presence or number of these files does not indicate that manual action is required. In SUSE Multi-Linux Manager container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation. Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.

14. 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 Uyuni tools version.

   cat /etc/os-release
   mgrpxy --version

   Confirm:

   • Operating System: SUSE Linux Enterprise Server 15 SP6

   • Tools version: mgrpxy version 0.1.29 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 Uyuni Server using the Web UI.

   For more information, see Software Products.

   Synchronize:

   • SUSE Linux Enterprise Server SP7

   • Uyuni Proxy Extension 2026.06

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 SP6 + SUSE Manager Proxy 5.0 Extension

     to:

   • SUSE Linux Enterprise Server SP7 + Uyuni Proxy Extension 2026.06

     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 Uyuni extension version:

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

8. Verify Uyuni tools version.

   mgrpxy --version

   Expected output:

   • mgrpxy version 5.2 or higher

9. Install the new proxy container images as RPM packages.

   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

    For air-gapped installations, first upgrade the container RPM packages, then run the mgrpxy upgrade podman command.

    Or, those running on a Kubernetes cluster can update using:

    mgrpxy upgrade kubernetes

12. Clean up the unused container images to free disk space:

    podman image prune -a

    In some upgrades, multiple *.rpmnew and *.rpmsave files may be generated. The presence or number of these files does not indicate that manual action is required. In SUSE Multi-Linux Manager container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation. Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.

13. 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