SUSE Multi-Linux Manager Proxy Upgrade
Before running the upgrade command, it is required to update the host operating system.
Updating the host operating system will also result in the update of the SUSE Multi-Linux Manager tooling such as the mgrpxy tool.
Refresh software repositories with
zypper:zypper refDepending on the host operating system, proceed with these steps:
- For a transactional system such as SL Micro:
Apply available updates with
transactional-update:transactional-updateIf updates were applied,
reboot.- For SUSE Linux Enterprise Server:
Update installed software with
zypper:zypper upThe SUSE Multi-Linux Manager Proxy containers running on
podmancan be updated using the following command:mgrpxy upgrade podmanOr, those running on a Kubernetes cluster can update using:
mgrpxy upgrade kubernetesOn podman, clean up the unused container images to free disk space:
podman image prune -aOn Kubernetes the image cleanup is handled automatically, or it depends on the Kubernetes distribution. ``
Check for
*.rpmnewand*.rpmsavefiles inside the container:mgrctl exec 'find /etc/ -name "*.rpmnew" -o -name "*.rpmsave"'
When an upgrade includes changes to a default configuration file that has been altered after package installation, instead of overwriting the file, one of these file types is created:
*.rpmnew: contains the new default configuration and leaves your altered file untouched
*.rpmsave: a copy of your altered configuration that has been replaced by the new default fileIf you find any
*.rpmnewor*.rpmsavefiles, examine their content and merge desirable changes.
|
If you do not specify the tag parameter when upgrading to specific version, it will default to upgrading to the most recent version. To upgrade to a specific version, provide the tag parameter with the desired image tag. |
|
While there is an option to upgrade a specific container using its specific tag, this feature is intended for applying PTFs only. We highly recommend using the same tag for all proxy containers to ensure consistency under normal circumstances. |
For air-gapped installations, first upgrade the container RPM packages, then run the mgrpxy upgrade podman command.