Red Hat Training

A Red Hat training course is available for Red Hat Virtualization

3.2. Upgrading to Red Hat Virtualization Manager 4.0

Red Hat Virtualization Manager 4.0 is only supported on Red Hat Enterprise Linux 7. A clean installation of Red Hat Enterprise Linux 7 and Red Hat Virtualization Manager 4.0 is required, even if you are using the same physical machine used to run Red Hat Enterprise Virtualization Manager 3.6. The upgrade process involves restoring Red Hat Enterprise Virtualization Manager 3.6 backup files onto the Red Hat Virtualization Manager 4.0 machine.

Important

All data centers and clusters in the environment must have the cluster compatibility level set to version 3.6 before attempting the procedure.

Important

Directory servers configured using the domain management tool are not supported after Red Hat Enterprise Virtualization 3.6. If your directory servers are configured using the domain management tool, migrate to the new extension-based provider before backing up the environment. See Migrating from the Legacy Provider to the New Extension-Based Provider in the Administration Guide for more information.
After the Manager has been upgraded, you can upgrade the hosts. See Chapter 2, Updates between Minor Releases. Then the cluster compatibility level can be updated to 4.0. See Chapter 4, Post-Upgrade Tasks."

Note

Connected hosts and virtual machines can continue to work while the Manager is being upgraded.
Use ovirt-engine-rename to rename the Manager only if the Manager has a different FQDN after the upgrade.
If any optional extension packages, such as ovirt-engine-extension-aaa-ldap, ovirt-engine-extension-aaa-misc, or ovirt-engine-extension-logger-log4j are installed on Red Hat Enterprise Virtualization Manager 3.6, these will need to be installed on the upgraded Manager before running engine-setup. The settings for these package extensions are not migrated as part of the upgrade.

Procedure 3.1. Upgrading to Red Hat Virtualization Manager 4.0

  1. On Red Hat Enterprise Virtualization Manager 3.6, back up the environment. 
    # engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log
  2. Copy the backup file to a suitable device.
  3. If the ISO storage domain is on the same host as the engine, back up the contents of /var/lib/exports/iso: 
    # cd /var/lib/exports/iso
# tar zcf iso_domain.tar.gz UUID
    The ISO storage backup file will be restored after the upgrade, in Section 3.3, “Migrating the ISO Domain” .
  4. Install Red Hat Enterprise Linux 7. See the Red Hat Enterprise Linux Installation Guide for more information.
  5. Install Red Hat Virtualization Manager 4.0. See the Red Hat Virtualization Installation Guide.
  6. Copy the backup file to the Red Hat Virtualization Manager 4.0 machine and restore it. 
    # engine-backup --mode=restore --file=backup.bck --log=restore.log --provision-db --provision-dwh-db --restore-permissions

    Note

    If the backup contained grants for extra database users, this command will create the extra users with random passwords. You must change these passwords manually if the extra users require access to the restored system. See https://access.redhat.com/articles/2686731.

    Note

    Use the --provision-dwh-db option if the backup contains Data Warehouse data.
    Reports have been deprecated in Red Hat Virtualization 4.0 and will not be restored. See BZ#1340810 for more information.
  7. Install optional extension packages if they were installed on the Red Hat Enterprise Virtualization Manager 3.6 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.
  8. Decommission the Red Hat Enterprise Virtualization Manager 3.6 machine if a different machine is used for Red Hat Virtualization Manager 4.0.
  9. Run engine-setup to configure the Manager. 
    # engine-setup
  10. Run ovirt-engine-rename to rename the Manager only if the FQDN differs from the Red Hat Enterprise Virtualization Manager 3.6 machine, and follow the prompts to set the new details. 
    # /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename

Note

If you use external CA to sign HTTPS certificates, follow the steps in Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide 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.
Before updating the Red Hat Enterprise Linux hosts in the environment, disable the version 3.6 repositories and enable the required 4.0 repository by running the following commands on the host you wish to update. 
# subscription-manager repos --disable=rhel-7-server-rhev-mgmt-agent-rpms
# subscription-manager repos --enable=rhel-7-server-rhv-4-mgmt-agent-rpms
RHEV-H hosts must be reinstalled with RHVH 4.0. See Red Hat Virtualization Hosts in the Installation Guide. However, if your environment has a local storage domain, use the instructions in Section 3.4, “Upgrading to RHVH While Preserving Local Storage” instead.
You may now update the hosts, then change the cluster and data center compatibility version to 4.0.