Server Upgrade from 5.0 to 5.2
|
Uyuni 5.0 must be stopped before the upgrade. |
|
Before upgrading to Uyuni 2026.10, you must update your Uyuni 5.0 Server to the latest available maintenance update, and ensure it is running (see Server Maintenance Update). Database schema migrations require intermediate changes from prior maintenance updates. Upgrading directly from an older maintenance update can cause database migration errors and server startup failure. |
|
For a list of known issues, see Uyuni Release Notes. |
|
Uyuni server hosts that are hardened for security may restrict execution of files from the For example:
In Uyuni updates, tools will be changed to make this workaround unnecessary. |
|
Before upgrading, verify that every root and intermediate CA certificate used by Uyuni marks If your installation uses an older self-signed CA generated by Uyuni, you might need to create a new CA and new server certificates, then deploy the new root CA to all clients. You can rotate the CA certificate on a Podman installation using the new Note that the command can only be used after upgrading both While failing to rotate the CA certificate may not cause an immediate system failure, it is strongly discouraged. |
SSL certificates are needed at a later stage. If not using the self-signed generated CA and certificates, ensure you have the following before starting:
-
A certificate authority (CA) SSL public certificate. If you are using a CA chain, all intermediate CAs must also be available.
-
An SSL database private key.
-
An SSL database certificate.
All files must be in PEM format.
The hostname of the SSL server certificate must match the fully qualified hostname of the machine you deploy them on.
You can set the hostnames in the X509v3 Subject Alternative Name section of the certificate.
You can also list multiple hostnames if your environment requires it.
Supported Key types are RSA and EC (Elliptic Curve).
|
In the past, database SSL certificate required |
The database container needs only the externally facing fully qualified domain name.
The old certificates with db and reportdb SANs can be still used.
The same certificate can be used for both the main container and the database one.
In order to pass the new certificates to the upgrade command, use the --ssl-db-ca-root, --ssl-db-cert and --ssl-db-key parameters.
|
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. |
During a migration the server SSL certificate and CA chain are copied from the source server.
1. SLE Micro 5.5 to SL Micro 6.2
This document provides the tested procedure to upgrade a SLE Micro 5.5 host deployed with Uyuni 5.0 Server to SL Micro 6.2 and migrate to Uyuni 2026.10.
1.1. Prerequisites
-
Uyuni 5.0 is installed and running on SLE Micro 5.5.
-
Uyuni 5.0 is updated to the latest available maintenance update, and running (see Server Maintenance Update).
-
System is registered and has active subscriptions with SCC.
1.2. Distribution upgrade and server migration
Verify current product status.
SUSEConnect --status-textConfirm:
Base OS:
SUSE Linux Enterprise Micro 5.5Extension:
SUSE Manager Server 5.0 ExtensionEnsure the host system is updated.
This step updates the host operating system packages and tooling (such as
mgradm). Ensure the Uyuni Server containers have already been updated to the latest maintenance update and are running before this procedure.transactional-update patch
If patches were applied, stop the server and then reboot the system before proceeding to migration:
mgradm stop rebootIf no updates were found, you can proceed directly to the migration step.
Start the migration.
transactional-update migration --auto-agree-with-licenses --gpg-auto-import-keysFollow the prompts and select the available migration to SUSE Linux Micro 6.2 and Uyuni Server Extension 2026.10.
Clean up the unused container images to free disk space:
podman image prune -a
In some upgrades, multiple
*.rpmnewand*.rpmsavefiles may be generated. The presence or number of these files does not indicate that manual action is required. In Uyuni container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation.Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.
Stop the server and then reboot to apply changes.
mgradm stop rebootPerform post-reboot checks.
Verify Uyuni extension and Uyuni version:
SUSEConnect --status-text mgradm --versionExpected output:
Extension:
SUSE Multi-Linux Manager Server 2026.10 ExtensionVersion: referencing
5.2.0or higherUpgrade server containers.
+
Before running
mgradm upgrade, check whether/etc/systemd/system/uyuni-server.servicecontains explicit IPv6 port bindings in the form-p [::]:PORT:PORT. These bindings are incompatible with netavark on SL Micro 6.2 and cause malformed nftables rules that prevent the web UI from being reachable after the upgrade.If such lines are present, remove them before proceeding:
-p 80:80 \ - -p [::]:80:80 \ -p 443:443 \ - -p [::]:443:443 \Then reboot the host before continuing:
systemctl rebootmgradm start mgradm upgradeFollow the prompts to pull and configure the new 5.2.x containers.
During an upgrade to version 5.2,
mgradm upgradeonly deploys the TFTP container on the server if TFTP was already enabled on the previous installation. Using a Uyuni Proxy is recommended for TFTP autoinstallation. To force deploying the TFTP container directly on the server, append the--tftpd-enableflag tomgradm upgrade.Verify running containers.
podman psExpected output:
server:5.2.0or higher
server-postgresql:5.2.0or higherClean up the unused container images to free disk space:
podman image prune -a
In some upgrades, multiple
*.rpmnewand*.rpmsavefiles may be generated. The presence or number of these files does not indicate that manual action is required. In Uyuni container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation.Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.
1.3. Migration complete
The server host system is now running SL Micro 6.2 with updated Uyuni 2026.10 Server packages.
If you have a Uyuni 5.0 proxy connected to this server, proceed to the Proxy Upgrade 5.0 > 5.2 guide to upgrade the proxy host.
Validate your setup before resuming production operations.
1.4. 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.
2. SUSE Linux Enterprise Server 15 SP6 to 15 SP7
This document provides the procedure to upgrade a SUSE Linux Enterprise Server 15 SP6 host deployed with Uyuni 5.0 Server to SUSE Linux Enterprise Server 15 SP7 and migrate to Uyuni 2026.10.
2.1. Prerequisites
-
Uyuni 5.0 is installed and running on SUSE Linux Enterprise Server 15 SP6.
-
Uyuni 5.0 is updated to the latest available maintenance update, and running (see Server Maintenance Update).
-
System is registered and has active subscriptions with SCC.
2.2. Distribution upgrade and server migration
Verify current product status.
SUSEConnect --status-textConfirm:
Base OS:
SUSE Linux Enterprise Server 15 SP6Extension:
SUSE Manager Server 5.0 ExtensionEnsure the host system is updated.
This step updates the host operating system packages and tooling (such as
mgradm). Ensure the Uyuni Server containers have already been updated to the latest maintenance update and are running before this procedure.zypper patchIf patches were applied, stop the server and then reboot before proceeding:
mgradm stop rebootPerform the migration to SP7 and Uyuni 2026.10.
zypper migrationSelect to migrate to:
SUSE Linux Enterprise Server 15 SP7
Uyuni Server Extension 2026.10Stop the server and reboot.
mgradm stop rebootPerform post-reboot checks.
Verify Uyuni extension:
SUSEConnect --status-textExpected output:
Extension:
SUSE Multi-Linux Manager Server 2026.10 ExtensionVerify Uyuni version.
mgradm --versionExpected output:
Version: referencing
5.2.0or higherUpgrade server containers.
+
mgradm start mgradm upgradeFollow the prompts to pull and configure the new 5.2.x containers.
During an upgrade to version 5.2,
mgradm upgradeonly deploys the TFTP container on the server if TFTP was already enabled on the previous installation. Using a Uyuni Proxy is recommended for TFTP autoinstallation. To force deploying the TFTP container directly on the server, append the--tftpd-enableflag tomgradm upgrade.Verify containers:
podman psExpected output:
server:5.2.0or higher
server-postgresql:5.2.0or higher
2.3. Migration complete
The server host system is now running SUSE Linux Enterprise Server 15 SP7 with updated Uyuni 2026.10 Server packages.
If you have a Uyuni 5.0 proxy connected to this server, proceed to the Proxy Upgrade 5.0 > 5.2 guide to upgrade the proxy host.
Validate your setup before resuming production operations.
2.4. 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.