Server Upgrade

1. Refresh software repositories with zypper:

   zypper ref

2. Apply available updates:

   1. For SLE Micro:

      transactional-update

      If updates were applied, reboot.

   2. For SUSE Linux Enterprise Server:

      zypper up

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

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

   podman image prune -a

5. Check for *.rpmnew and *.rpmsave files 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 file

6. If you find any *.rpmnew or *.rpmsave files, examine their content and merge desirable changes.