Server - Minor Upgrade

Several times a year, the Uyuni team releases minor upgrades of the Uyuni Server. These updates address bug fixes and feature improvements, and sometimes include new features.

Some additional manual steps might be required, and this information is only available in the release notes. For important extra information about your upgrade, see the release notes at

Performing a minor upgrade is similar to installing operating system package updates.

Procedure: Updating Packages on the Uyuni Server

By default, several update repositories are configured and enabled for the Uyuni Server. New and updated packages become available automatically.

It is recommended you make a backup of the server before upgrading. For more information about backing up Uyuni, see administration:backup-restore.adoc.

  1. On the Uyuni Server, at the command prompt, as root, stop the spacewalk services:

    spacewalk-service stop
  2. Refresh software repositories:

    zypper ref
  3. Update new packages: (Repeat this if prompted by zypper)

    zypper up
  4. If zypper reports that the Uyuni package won’t be upgraded, run the command manually:

    zypper install Uyuni-Server-release
  5. Restart the spacewalk services:

    spacewalk-service start

    Reboot the server if a patch update recommends rebooting.

By default, zypper refreshes the repository every ten minutes (see repo.refresh.delay in /etc/zypp/zypp.conf). If autorefresh is disabled, run zypper ref to refresh all repositories.

Starting with Uyuni 2020.04 spacewalk-schema-upgrade is not needed anymore.

The schema upgrade is run automatically when the spacewalk service is started with spacewalk-service start.

Services affected by a package update are not automatically restarted after an update. You need to restart these services manually to avoid potential failures. Use zypper ps to check for applications that are using old code and require restarting.