Uyuni Server Upgrade
Before running the upgrade command, it is recommended to to update the host operating system.
Updating the host operating system will also result in the update of the Uyuni tooling such as the mgradm
tool.
-
Refresh software repositories with
zypper
:zypper ref
-
Apply available updates with
transactional-update
:transactional-update
-
If updates were applied,
reboot
. -
The Uyuni Server container can be updated using the following command:
mgradm upgrade podman
This command will bring the status of the container up-to-date and restart the server.
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:
mgradm upgrade podman -h
For air-gapped installations, first upgrade the container RPM packages, then run the mgradm
command.
1. Database Backup Volume
Server migration or upgrade with mgradm migration
or mgradm upgrade
can create a volume with the database backup.
When the PostgreSQL database version is increased, the old database must be stored in a separate location before running the upgrade.
For this purpose mgradm
dynamically creates the volume var-pgsql-backup
.
When the migration or upgrade is done and the user has validated that the new system is working as expected, this volume can be removed safely.