Server Upgrade

Before running the upgrade command, it is required to upgrade the mgradm tool first.

Procedure: Upgrading Server

Refresh software repositories with zypper:
zypper ref
Apply available updates:
For SLE Micro:
transactional-update
If updates were applied, reboot.
For SUSE Linux Enterprise Server:
zypper up
The SUSE Manager Server container can be updated using the following command:

Risk of Automated Version Downgrade and PTF Loss

Running the mgradm upgrade podman command when no newer upgrade is available will cause the system to automatically revert to the base version. This process removes all currently applied Program Temporary Fixes (PTFs) without a confirmation prompt.

To avoid unintended data or fix loss, verify upgrade availability before execution. Future releases will include a confirmation prompt to prevent this behavior.
mgradm upgrade podman
+

This command will bring the status of the container up-to-date and restart the server.

+
Clean up the unused container images to free disk space:
podman image prune -a

Upgrading to specific version

If you do not specify the tag parameter, 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.

For more information on the upgrade command and its parameters, use the following command:

Risk of Automated Version Downgrade and PTF Loss

Running the mgradm upgrade podman command when no newer upgrade is available will cause the system to automatically revert to the base version. This process removes all currently applied Program Temporary Fixes (PTFs) without a confirmation prompt.

To avoid unintended data or fix loss, verify upgrade availability before execution. Future releases will include a confirmation prompt to prevent this behavior.

mgradm upgrade podman -h

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