6.6. Upgrading the Red Hat Virtualization Manager from 4.3 to 4.4

The Red Hat Virtualization Manager 4.4 is only supported on Red Hat Enterprise Linux 8.2 or later. You need to do a clean installation of Red Hat Enterprise Linux 8.2 or Red Hat Virtualization Host on the self-hosted engine host, even if you are using the same physical machine that you use to run the RHV 4.3 self-hosted engine.

The upgrade process requires restoring Red Hat Virtualization Manager 4.3 backup files onto the Red Hat Virtualization Manager 4.4 virtual machine.

Prerequisites

  • All data centers and clusters in the environment must have the cluster compatibility level set to version 4.2 or 4.3 before you start the procedure.
  • Make note of the MAC address of the self-hosted engine if you are using DHCP and want to use the same IP address. The deploy script prompts you for this information.
  • During the deployment you need to provide a new storage domain for the Manager machine. The deployment script renames the 4.3 storage domain and retains its data to enable disaster recovery.

    Caution

    In an environment with multiple highly available self-hosted engine nodes, you need to detach the storage domain hosting the version 4.3 Manager after upgrading the Manager to 4.4. Use a dedicated storage domain for the 4.4 self-hosted engine deployment.

  • If you use an external CA to sign HTTPS certificates, follow the steps in Replacing the Red Hat Virtualization Manager CA Certificate in the Administration Guide. The backup and restore include the 3rd-party certificate, so you should be able to log in to the Administration portal after the upgrade. Ensure the CA certificate is added to system-wide trust stores of all clients to ensure the foreign menu of virt-viewer works. See BZ#1313379 for more information.
Note

Connected hosts and virtual machines can continue to work while the Manager is being upgraded.

Procedure

  1. Log in to the Manager host machine.
  2. Log in to the Manager virtual machine and shut down the engine service.

    # systemctl stop ovirt-engine
  3. Back up the Red Hat Virtualization Manager 4.3 environment.

    # engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log
  4. Copy the backup file to a storage device outside of the RHV environment.
  5. Install RHVH 4.4 or Red Hat Enterprise Linux 8.2 or later on the node to use it as the self-hosted engine deployment host. See Installing the Self-hosted Engine Deployment Host for more information.
  6. Install the self-hosted engine deployment tool.

    # yum install ovirt-hosted-engine-setup
  7. Copy the backup file to the host.
  8. Log in to the Manager host and deploy the self-hosted engine with the backup file:

    # hosted-engine --deploy --restore-from-file=/path/backup.bck
    Note

    tmux enables the deployment script to continue if the connection to the server is interrupted, so you can reconnect and attach to the deployment and continue. Otherwise, if the connection is interrupted during deployment, the deployment fails.

    To run the deployment script using tmux, enter the tmux command before you run the deployment script:

    # tmux
    # hosted-engine --deploy --restore-from-file=backup.bck

    The deployment script automatically disables global maintenance mode and calls the HA agent to start the self-hosted engine virtual machine. The upgraded host with the 4.4 self-hosted engine reports that HA mode is active, but the other hosts report that global maintenance mode is still enabled as they are still connected to the old self-hosted engine storage.

  9. Detach the storage domain that hosts the Manager 4.3 machine. For details, see Detaching a Storage Domain from a Data Center in the Administration Guide.
  10. Log in to the Manager virtual machine and shut down the engine service.

    # systemctl stop ovirt-engine
  11. Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine.

    # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j
    Note

    The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process.

The Red Hat Virtualization Manager 4.4 is now installed, with the cluster compatibility version set to 4.2 or 4.3, whichever was the preexisting cluster compatibility version.

You can now update the self-hosted engine nodes, and then any standard hosts. The procedure is the same for both host types.