Upgrading from Version 4 to 4.x

You can upgrade Uyuni from version 4 to 4.x (when available) using either the YaST online migration tool or the Zypper command line tool. This procedure is also known as SP migration (service pack migration). This procedure does not replace the server with an updated copy. It is an in-place upgrade.

Example: 4.0.x → 4.1.0.

The upgrade from version 4 to 4.1 will also upgrade the base OS from SLES 15 SP1 to SLES 15 SP2, and the PostgreSQL database from version 10 to 12 with an additional step.

Upgrades should be run from a text console, rather than a graphical interface like GNOME. If you are logged into a GNOME session running on the machine you are going to migrate, you will need to switch to a text console. This does not apply if you are logged in from a remote machine (unless you are running a VNC session with GNOME).

Upgrade Using YaST

To perform the upgrade with YaST, use the Online Migration tool.

If YaST does not have the Online Migration tool available, install the yast2-migration package and all the required packages. After installing, restart YaST to ensure the tool is available within YaST.

Procedure: Upgrading with YaST

From the command prompt, as root, launch the YaST online migration tool:
```
yast2 migration
```
If there are older updates available, YaST will notify you and ask to install them first. You must install all package updates before performing the migration. For more information, see server-update.adoc.

YaST will show the possible migration targets with detailed summaries.
Select the appropriate target, and follow the prompts to complete the migration.
Reboot the server.
When rebooted the spacewalk services are not running until you have migrated the PostgreSQL database to version 12.
Log in on the text console as root, and run the database migration script:
```
/usr/lib/susemanager/bin/pg-migrate-10-to-12.sh
```
Ensure the spacewalk services are running:
```
spacewalk-service start
```
spacewalk-schema-upgrade is not needed anymore. It will be run during spacewalk-service start automatically.

During the upgrade, YaST will install all recommended packages. This can significantly increase the installation size of the system. To only install required packages, open the /etc/zypp/zypp.conf configuration file and set these variables:

solver.onlyRequires = true
installRecommends = false

This changes the behavior of all future package operations.

Upgrade Using Zypper

To perform the upgrade with Zypper, use the Zypper migration tool.

Procedure: Upgrading with Zypper

From the command prompt, as root, launch the Zypper migration tool:
```
zypper migration
```
Zypper will show the possible migration targets with detailed summaries.
Select the appropriate target, and follow the prompts to complete the migration.
Reboot the server.
When rebooted the spacewalk services are not running until you have migrated the PostgreSQL database to version 12.
Log in on the text console as root, and run the database migration script:
```
/usr/lib/susemanager/bin/pg-migrate-10-to-12.sh
```
Ensure the spacewalk services are running:
```
spacewalk-service start
```
spacewalk-schema-upgrade is not needed anymore. It will be run during spacewalk-service start automatically.

If the process fails, check these issues first:

If Zypper does not have the migration tool available, install the zypper-migration-plugin package.
If there are older updates available, Zypper will notify you and ask to install them first. You must install all updates before performing the upgrade.

Troubleshooting

If the schema upgrade fails, the database version check and all the other spacewalk services do not start. Run spacewalk-service start for more information and hints how to proceed. You can run the version check directly:

systemctl status uyuni-check-database.service

journalctl -u uyuni-check-database.service

These print debug information if you do not use the spacewalk-service command.

Effective with SUMA 4.1 Beta 3 @mcalmer mcalmer added documentation docs-squad labels 10 days ago