Upgrading the Engine or Self-Hosted Engine

Upgrade a standalone or Self-Hosted Engine on Oracle Linux 8

Important:

This section applies only when you upgrade an Oracle Linux 8 standalone or Self-Hosted Engine from Oracle Linux Virtualization Manager Release 4.4 to 4.5.

Before you start the upgrade process,

  • Review the environment upgrade overview.
  • Familiarize yourself with appliance package versions required depending on the Oracle Linux version used for host or engine.

    Table 6-1 Self-Hosted Engine Installation packages

    KVM-Host Engine Package
    Oracle Linux 8 Oracle Linux 8 engine ovirt-engine-appliance-4.5-20240306.x.x.x.el8.x86_64
    Oracle Linux 8

    Oracle Linux 9 engine

    ovirt-engine-appliance-4.5-20260211.x.x.x.el8.x86_64
    Oracle Linux 9 Oracle Linux 8 engine ovirt-engine-appliance-4.5-20240306.x.x.x.el9.x86_64
    Oracle Linux 9 Oracle Linux 9 engine ovirt-engine-appliance-4.5-20260211.x.x.x.el9.x86_64
  • Verify that you have satisfied the prerequisites.
  • Ensure you have updated engine or self-hosted engine to latest version of 4.4.
  • Ensure you have updated KVM hosts to the latest version of 4.4.
  1. On the engine or self-hosted engine machine, install the Oracle Linux Virtualization Manager Release 4.5 package.
    dnf install oracle-ovirt-release-45-el8
  2. Verify that the ovirt-4.5 and ovirt-4.5-extras repositories are enabled.
    dnf repolist

    If either repository isn't enabled, use the dnf config-manager --enable repository command to enable them.

    Note:

    For ULN registered hosts or if you're using Oracle Linux Manager, ensure you have subscribed to ol8_x86_64_ovirt45 and ol8_x86_64_ovirt45_extras.
  3. Check for updated packages:

    engine-upgrade-check
  4. Update the setup packages:

    dnf update ovirt\*setup\*
  5. Check the engine host configuration or the self-hosted engine host configuration.
  6. Update the engine or self-hosted engine:

    engine-setup
  7. Proceed to Migrating KVM Hosts to 4.5.

    Important:

    After the engine and KVM hosts are upgraded and verified, remove the release package for version 4.4 on engine and all KVM hosts:
    dnf remove oracle-ovirt-release-el8

Upgrade a Self-Hosted Engine Installation from Oracle Linux 8 to Oracle Linux 9

Important:

This section applies only when you replace an Oracle Linux 8 Self-Hosted Engine virtual machine with an Oracle Linux 9 Self-Hosted Engine virtual machine. An in-place upgrade of the Engine virtual machine operating system is not supported.

Create a full backup of the Oracle Linux 8 Engine virtual machine and restore it during deployment of a replacement Oracle Linux 9 Engine virtual machine. The backup procedure is the same as for a standalone engine. Run commands as root on the machine specified in each step.

Before you start, verify that the source Engine is at the required Oracle Linux Virtualization Manager 4.5 update level. Prepare an Oracle Linux 9 KVM deployment host with a compatible deployment tool and an Oracle Linux 9 Engine Appliance that supports restoring the source Engine version. Preserve the original Engine FQDN and verify forward and reverse DNS. If you use a new deployment host, give it a unique host name.

Prepare new, empty storage for the replacement self-hosted engine storage domain. Preserve the original Engine virtual machine and its storage for recovery. The Manager backup does not include virtual machine disks on data storage domains.

  1. Sign in to the KVM host hosting the Engine virtual machine, enable global maintenance mode, and confirm the status.

    hosted-engine --set-maintenance --mode=global
    hosted-engine --vm-status

    Verify that the status includes Cluster is in GLOBAL MAINTENANCE mode. Keep the original environment in global maintenance mode during the replacement.

  2. Sign in to the Oracle Linux 8 Engine virtual machine and stop the engine service to prevent changes during the final backup.

    systemctl stop ovirt-engine
  3. On the Engine virtual machine, create a full backup.

    engine-backup --mode=backup --scope=all

    Record the backup file and log file paths reported by the command. Confirm that the backup completes with Done.. To specify the paths, use the --file and --log options. See Backing Up the Manager.

  4. Verify the backup and record its checksum on the Engine virtual machine.

    engine-backup --mode=verify --file=backup_file
    sha256sum backup_file

    Replace backup_file with the full path to the backup archive.

  5. Transfer the backup archive and its log file from the Engine virtual machine to a secure directory on the KVM host hosting the Engine virtual machine.

    scp -p backup_file backup_log root@kvm_host:backup_directory/

    If you restore on a different deployment host, also copy the archive to that host. Restrict access to the backup files and compare the archive checksum on the deployment host with the checksum recorded on the Engine virtual machine.

  6. After verifying the transferred backup, shut down the original Engine virtual machine.

    systemctl poweroff

    WARNING:

    Ensure that the original Engine virtual machine cannot restart before you deploy the replacement. Only one Engine can manage the same hosts and storage domains.

  7. On the prepared Oracle Linux 9 KVM deployment host, install the deployment tool and the Oracle Linux 9 Engine Appliance from the configured Oracle Linux Virtualization Manager 4.5 repositories.

    dnf install ovirt-hosted-engine-setup ovirt-engine-appliance

    Before entering yes to proceed with the installation, ensure the package version is for Oracle Linux 9 by confirming the version ends with el9.

    Verify that correct appliance package is installed depending on the Oracle Linux version used for host or engine. For the version and package combinations, see the table at Table 6-1.

    Verify that the selected appliance provides Oracle Linux 9. For host configuration prerequisites, see Deploy the Self-Hosted Engine.

  8. On the KVM deployment host, deploy the replacement Engine virtual machine and restore the backup.

    hosted-engine --deploy --4 --restore-from-file=backup_file

    Use the full path to the verified backup archive on the deployment host. The --4 option selects IPv4. Follow the deployment prompts, use the original Engine FQDN, and select the new, empty self-hosted engine storage. Do not select the original self-hosted engine storage or an existing data storage domain.

    If deployment pauses because the host is nonoperational, use the temporary Administration Portal URL displayed by the deployment tool to configure the required logical networks. Continue only after the host is up.

  9. After deployment completes successfully, verify the restored Engine status on the deployment host.

    hosted-engine --vm-status

    Confirm that the Engine status reports:

    {"health": "good", "vm": "up", "detail": "Up"}

    Sign in to the replacement Engine virtual machine, confirm that it runs Oracle Linux 9, and verify that the engine service is active.

    cat /etc/oracle-release
    systemctl is-active ovirt-engine
  10. Sign in to the Administration Portal and verify host connectivity, data storage domains, logical networks, virtual machine inventory, and authentication. Confirm the existing data center and cluster compatibility levels. Configure additional compatible self-hosted engine hosts for the restored environment before relying on high availability.

  11. Create and verify a new full backup from the restored Engine virtual machine. Retain the original Engine and the final Oracle Linux 8 backup until validation is complete.

WARNING:

Changes made after the backup was created are not included in the restored Manager. If recovery requires returning to the original Engine, first shut down and isolate the replacement Engine and prevent its HA agents from restarting it.

For KVM host migration, see Migrate KVM Hosts from Oracle Linux 8 to Oracle Linux 9. For compatibility versions, see Changing Data Center and Cluster Compatibility Versions After Upgrading.

Migrate a standalone engine from Oracle Linux 8 to Oracle Linux 9

Important:

This section applies only when you move a standalone Manager from Oracle Linux 8 to Oracle Linux 9. An in-place upgrade of the Manager host operating system is not supported.

Back up the Oracle Linux 8 Manager and restore it on a new or re-imaged Oracle Linux 9 host. Preserve the Oracle Linux 8 boot volume until you validate the restored Manager.

  1. Verify the Manager is at the required 4.5 package and build level.

  2. Stop the engine service and create a full backup.

    sudo systemctl stop ovirt-engine
    sudo engine-backup --mode=backup --scope=all
  3. Copy the backup file to secure storage. Record its location and verify that the copy is readable.

  4. Install and configure a standalone Oracle Linux 9 Manager host. See Configure an Oracle Linux 9 Engine Host.

  5. Restore the backup and configure the Manager.

    sudo engine-backup --mode=restore --file=backup_file --provision-all-databases --restore-permissions
    sudo engine-setup
  6. Validate the restored environment. Verify the service status, sign in to the Administration Portal, verify host connectivity, confirm data center and cluster compatibility, verify that running virtual machines report the expected state, and verify the backup archive.

WARNING:

Objects changed after the backup was created are not included in the restored Manager. Recover or recreate those objects as necessary. If validation fails, return to the retained Oracle Linux 8 boot volume and restore the original backup.

Before you start the upgrade process,

  1. On the engine or self-hosted engine machine, install the Oracle Linux Virtualization Manager Release 4.5 package.
    dnf install oracle-ovirt-release-45-el8
  2. Verify that the ovirt-4.5 and ovirt-4.5-extras repositories are enabled.
    dnf repolist

    If either repository isn't enabled, use the dnf config-manager --enable repository command to enable them.

    Note:

    For ULN registered hosts or if you're using Oracle Linux Manager, ensure you have subscribed to ol8_x86_64_ovirt45 and ol8_x86_64_ovirt45_extras.
  3. Check for updated packages:

    engine-upgrade-check
  4. Update the setup packages:

    dnf update ovirt\*setup\*
  5. Check the engine host configuration or the self-hosted engine host configuration.
  6. Update the engine or self-hosted engine:

    engine-setup
  7. Proceed to Migrating KVM Hosts to 4.5.

    Important:

    After the engine and KVM hosts are upgraded and verified, remove the release package for version 4.4 on engine and all KVM hosts:
    dnf remove oracle-ovirt-release-el8