Chapter 5. Updating the Red Hat Enterprise Virtualization Environment

This chapter covers both updating your Red Hat Enterprise Virtualization environment between minor releases, and upgrading to the next major version. Always update to the latest minor version of your current Red Hat Enterprise Virtualization Manager version before you upgrade to the next major version.
For interactive upgrade instructions, you can also use the RHEV Upgrade Helper available at https://access.redhat.com/labs/rhevupgradehelper/. This application asks you to provide information about your upgrade path and your current environment, and presents the relevant steps for upgrade as well as steps to prevent known issues specific to your upgrade scenario.

5.1. Updates between Minor Releases

5.1.1. Checking for Red Hat Enterprise Virtualization Manager Updates

Important

Always update to the latest minor version of your current Red Hat Enterprise Virtualization Manager version before you upgrade to the next major version.

Procedure 5.1. Checking for Red Hat Enterprise Virtualization Manager Updates

  1. Run the following command on the machine on which the Red Hat Enterprise Virtualization Manager is installed:
    # engine-upgrade-check
    • If there are no updates are available, the command will output the text No upgrade:
      # engine-upgrade-check
      VERB: queue package rhevm-setup for update
      VERB: package rhevm-setup queued
      VERB: Building transaction
      VERB: Empty transaction
      VERB: Transaction Summary:
      No upgrade
    • If updates are available, the command will list the packages to be updated:
      # engine-upgrade-check
      VERB: queue package rhevm-setup for update
      VERB: package rhevm-setup queued
      VERB: Building transaction
      VERB: Transaction built
      VERB: Transaction Summary:
      VERB:     updated    - rhevm-lib-3.3.2-0.50.el6ev.noarch
      VERB:     update     - rhevm-lib-3.4.0-0.13.el6ev.noarch
      VERB:     updated    - rhevm-setup-3.3.2-0.50.el6ev.noarch
      VERB:     update     - rhevm-setup-3.4.0-0.13.el6ev.noarch
      VERB:     install    - rhevm-setup-base-3.4.0-0.13.el6ev.noarch
      VERB:     install    - rhevm-setup-plugin-ovirt-engine-3.4.0-0.13.el6ev.noarch
      VERB:     updated    - rhevm-setup-plugins-3.3.1-1.el6ev.noarch
      VERB:     update     - rhevm-setup-plugins-3.4.0-0.5.el6ev.noarch
      Upgrade available
      
      Upgrade available

5.1.2. Updating the Red Hat Enterprise Virtualization Manager

Updates to the Red Hat Enterprise Virtualization Manager are released via the Content Delivery Network. Before installing an update from the Content Delivery Network, ensure you read the advisory text associated with it and the latest version of the Red Hat Enterprise Virtualization Manager Release Notes and Red Hat Enterprise Virtualization Technical Notes on the Customer Portal. A number of actions must be performed to complete an upgrade, including:
  • Stopping the ovirt-engine service.
  • Downloading and installing the updated packages.
  • Backing up and updating the database.
  • Performing post-installation configuration.
  • Starting the ovirt-engine service.

Procedure 5.2. Updating Red Hat Enterprise Virtualization Manager

  1. Run the following command to update the rhevm-setup package:
    # yum update rhevm-setup
  2. Run the following command to update the Red Hat Enterprise Virtualization Manager:
    # engine-setup

Important

Active hosts are not updated by this process and must be updated separately. As a result, the virtual machines running on those hosts are not affected.

Important

The update process may take some time; allow time for the update process to complete and do not stop the process once initiated. Once the update is complete, you will also be instructed to separately update the Data Warehouse and Reports functionality. These additional steps are only required if you installed these features.

5.1.3. Updating Red Hat Enterprise Virtualization Hypervisors

Updating Red Hat Enterprise Virtualization Hypervisors involves reinstalling the Hypervisor with a newer version of the Hypervisor ISO image. This includes stopping and restarting the Hypervisor. If migration is enabled at cluster level, virtual machines are automatically migrated to another host in the cluster; as a result, it is recommended that Hypervisor updates are performed at a time when the Hypervisor's usage is relatively low.
Ensure that the cluster to which the host belongs has sufficient memory reserve in order for its hosts to perform maintenance. If a cluster lacks sufficient memory, the virtual machine migration operation will hang and then fail. You can reduce the memory usage of this operation by shutting down some or all virtual machines before updating the Hypervisor.
It is recommended that administrators update Red Hat Enterprise Virtualization Hypervisors regularly. Important bug fixes and security updates are included in updates. Hypervisors that are not up to date may be a security risk.

Important

Ensure that the cluster contains more than one host before performing an upgrade. Do not attempt to reinstall or upgrade all the hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.

Procedure 5.3. Updating Red Hat Enterprise Virtualization Hypervisors

  1. Log in to the system hosting Red Hat Enterprise Virtualization Manager as the root user.
  2. Enable the Red Hat Enterprise Virtualization Hypervisor (v.6 x86_64) repository:
    # subscription-manager repos --enable=rhel-6-server-rhevh-rpms
  3. Ensure that you have the most recent version of the rhev-hypervisor6 package installed:
    # yum update rhev-hypervisor6
  4. From the Administration Portal, click the Hosts tab, and then select the Hypervisor that you intend to upgrade.
    • If the Hypervisor requires updating, an alert message in the details pane indicates that a new version of the Red Hat Enterprise Virtualization Hypervisor is available.
    • If the Hypervisor does not require updating, no alert message is displayed and no further action is required.
  5. Click Maintenance. If automatic migration is enabled, this causes any virtual machines running on the Hypervisor to be migrated to other hosts. If the Hypervisor is the SPM, this function is moved to another host.
  6. Click Upgrade to open the Upgrade Host confirmation window.
  7. Select rhev-hypervisor.iso, which is symbolically linked to the most recent Hypervisor image.
  8. Click OK to update and reinstall the Hypervisor. The details of the Hypervisor are updated in the Hosts tab, and the status will transition through these stages:
    • Maintenance
    • Installing
    • Non Responsive
    • Up
    These are all expected, and each stage will take some time.
  9. Restart the Hypervisor to ensure all updates are correctly applied.
Once successfully updated, the Hypervisor displays a status of Up. Any virtual machines that were migrated off the Hypervisor are, at this point, able to be migrated back to it. Repeat the update procedure for each Hypervisor in the Red Hat Enterprise Virtualization environment.

Important

After a Red Hat Enterprise Virtualization Hypervisor is successfully registered to the Red Hat Enterprise Virtualization Manager and then upgraded, it may erroneously appear in the Administration Portal with the status of Install Failed. Click Activate, and the Hypervisor will change to an Up status and be ready for use.

5.1.4. Updating Red Hat Enterprise Linux Virtualization Hosts

Red Hat Enterprise Linux hosts use the yum command in the same way as regular Red Hat Enterprise Linux systems. It is highly recommended that you use yum to update your systems regularly, to ensure timely application of security and bug fixes. Updating a host includes stopping and restarting the host. If migration is enabled at cluster level, virtual machines are automatically migrated to another host in the cluster; as a result, it is recommended that host updates are performed at a time when the host's usage is relatively low.
The cluster to which the host belongs must have sufficient memory reserve in order for its hosts to perform maintenance. Moving a host with live virtual machines to maintenance in a cluster that lacks sufficient memory causes any virtual machine migration operations to hang and then fail. You can reduce the memory usage of this operation by shutting down some or all virtual machines before moving the host to maintenance.

Important

Ensure that the cluster contains more than one host before performing an update. Do not attempt to reinstall or update all the hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.

Procedure 5.4. Updating Red Hat Enterprise Linux Hosts

  1. From the Administration Portal, click the Hosts tab and select the host to be updated.
  2. Click Maintenance to place the host into maintenance mode.
  3. On the Red Hat Enterprise Linux host machine, run the following command:
    # yum update
  4. Restart the host to ensure all updates are correctly applied.
You have successfully updated the Red Hat Enterprise Linux host. Repeat this process for each Red Hat Enterprise Linux host in the Red Hat Enterprise Virtualization environment.