Proxy Upgrade from 5.1 to 5.2

1. 校验系统和 SUSE Multi-Linux Manager 工具版本。

   cat /etc/os-release
   mgrpxy --version

   确认以下信息：

   • Operating System: SL Micro 6.1

   • Tools version: mgrpxy version 5.1.x or higher

2. 检查正在运行的容器。

   podman ps

   确保以下容器正在运行：

   • proxy-squid

   • proxy-ssh

   • proxy-httpd

   • proxy-tftpd

   • proxy-salt-broker

3. 在 SUSE Multi-Linux Manager 服务器中同步新代理产品。有关详细信息，请参见 软件产品。

   使用 Web UI 进行同步：

   • SL Micro 6.2

   • SUSE Multi-Linux Manager Proxy Extension 5.2

4. 执行代理产品迁移。有关详细信息，请参见 产品迁移。

   导航至代理系统，选择系统  概览 > 软件  产品迁移。

   将

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

     迁移到

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

     出现提示时，请勿选择可选通道，除非您已确认必须使用这些通道。

     建议在执行实际迁移前先进行试运行。

5. 监控迁移操作。

   您可在 Web UI 的系统  细节  事件选项卡中查看流程进度。

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

   mgrpxy stop
   reboot

7. 执行重引导后的检查。

   校验升级后的操作系统和 SUSE Multi-Linux Manager 扩展：

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

8. 校验 SUSE Multi-Linux Manager 工具版本。

   mgrpxy --version

   预期输出：

   • 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. 重引导代理。

11. 升级代理容器并重启。

    mgrpxy upgrade podman
    mgrpxy stop
    mgrpxy start

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

    或者，可使用以下命令更新 Kubernetes 群集上运行的容器：

    mgrpxy upgrade kubernetes

12. 清理未使用的容器映像以释放磁盘空间：

    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. 确认代理容器可正常运行。

    podman ps

    所有预期的代理容器均应正常启动并运行：

    • proxy-salt-broker

    • proxy-httpd

    • proxy-squid

    • proxy-tftpd

    • proxy-ssh

1. 校验操作系统和 SUSE Multi-Linux Manager 工具版本。

   cat /etc/os-release
   mgrpxy --version

   确认以下信息：

   • Operating System: SUSE Linux Enterprise Server 15 SP7

   • Tools version: mgrpxy version 5.1.x or higher

2. 列出正在运行的代理容器。

   podman ps

   确保以下容器正在运行：

   • 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 软件产品.

   Synchronize:

   • SUSE Multi-Linux Manager Proxy Extension 5.2

4. Perform proxy product migration.

   For more information, see 产品迁移.

   导航至代理系统，选择系统  概览 > 软件  产品迁移。

   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

     出现提示时，请勿选择可选通道，除非您已确认必须使用这些通道。

     建议在执行实际迁移前先进行试运行。

5. 监控迁移操作。

   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. 执行重引导后的检查。

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

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

8. 校验 SUSE Multi-Linux Manager 工具版本。

   mgrpxy --version

   预期输出：

   • 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. 重引导代理。

11. 升级代理容器并重启。

    mgrpxy upgrade podman
    mgrpxy stop
    mgrpxy start

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

    或者，可使用以下命令更新 Kubernetes 群集上运行的容器：

    mgrpxy upgrade kubernetes

12. 清理未使用的容器映像以释放磁盘空间：

    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. 确认代理容器可正常运行。

    podman ps

    所有预期的代理容器均应正常启动并运行：

    • proxy-salt-broker

    • proxy-httpd

    • proxy-squid

    • proxy-tftpd

    • proxy-ssh