15.3. Upgrading to Red Hat Enterprise Virtualization 3.4
15.3.1. Red Hat Enterprise Virtualization Manager 3.4 Upgrade Overview
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.
The process for upgrading Red Hat Enterprise Virtualization Manager comprises three main steps:
- Subscribing to entitlements.
- Updating the required packages.
- Performing the upgrade.
The command used to perform the upgrade itself is
engine-setup, which provides an interactive interface. While the upgrade is in process, virtualization hosts and the virtual machines running on those virtualization hosts continue to operate independently. When the upgrade is complete, you can then upgrade your hosts to the latest versions of Red Hat Enterprise Linux or Red Hat Enterprise Virtualization Hypervisor.
15.3.2. Features Requiring a Compatibility Upgrade to Red Hat Enterprise Virtualization 3.4
Some of the features provided by Red Hat Enterprise Virtualization 3.4 are only available if your data centers, clusters, and storage have a compatibility version of 3.4.
Table 15.2. Features Requiring a Compatibility Upgrade to Red Hat Enterprise Virtualization 3.4
| Feature | Description |
|---|---|
|
Abort migration on error
|
This feature adds support for handling errors encountered during the migration of virtual machines.
|
|
Forced Gluster volume creation
|
This feature adds support for allowing the creation of Gluster bricks on root partitions. With this feature, you can choose to override warnings against creating bricks on root partitions.
|
|
Management of asynchronous Gluster volume tasks
|
This feature provides support for managing asynchronous tasks on Gluster volumes, such as rebalancing volumes or removing bricks. To use this feature, you must use GlusterFS version 3.5 or above.
|
|
Import Glance images as templates
|
This feature provides support for importing images from an OpenStack image service as templates.
|
|
File statistic retrieval for non-NFS ISO domains
|
This feature adds support for retrieving statistics on files stored in ISO domains that use a storage format other than NFS, such as a local ISO domain.
|
|
Default route support
|
This feature adds support for ensuring that the default route of the management network is registered in the main routing table and that registration of the default route for all other networks is disallowed. This ensures the management network gateway is set as the default gateway for hosts.
|
|
Virtual machine reboot
|
This feature adds support for rebooting virtual machines from the User Portal or Administration Portal via a new button. To use this action on a virtual machine, you must install the guest tools on that virtual machine.
|
15.3.3. Red Hat Enterprise Virtualization 3.4 Upgrade Considerations
The following is a list of key considerations that must be made when planning your upgrade.
Important
- Upgrading to version 3.4 can only be performed from version 3.3
- To upgrade a previous version of Red Hat Enterprise Virtualization earlier than Red Hat Enterprise Virtualization 3.3 to Red Hat Enterprise Virtualization 3.4, you must sequentially upgrade to any newer versions of Red Hat Enterprise Virtualization before upgrading to the latest version. For example, if you are using Red Hat Enterprise Virtualization 3.2, you must upgrade to Red Hat Enterprise Virtualization 3.3 before you can upgrade to Red Hat Enterprise Virtualization 3.4.
- Red Hat Enterprise Virtualization Manager cannot be installed on the same machine as IPA
- An error message displays if the ipa-server package is installed. Red Hat Enterprise Virtualization Manager 3.4 does not support installation on the same machine as Identity Management (IdM). To resolve this issue, you must migrate the IdM configuration to another system before re-attempting the upgrade.
- Upgrading to JBoss Enterprise Application Platform 6.2 is recommended
- Although Red Hat Enterprise Virtualization Manager 3.4 supports Enterprise Application Platform 6.1.0, upgrading to the latest supported version of JBoss is recommended.
- Reports and the Data Warehouse are now installed via
engine-setup - From Red Hat Enterprise Virtualization 3.4, the Reports and Data Warehouse features are configured and upgraded using the
engine-setupcommand. If you have configured the Reports and Data Warehouse features in your Red Hat Enterprise Virtualization 3.3 environment, you must install the rhevm-reports-setup and rhevm-dwh-setup packages prior to upgrading to Red Hat Enterprise Virtualization 3.4 to ensure these features are detected byengine-setup.
15.3.4. Upgrading to Red Hat Enterprise Virtualization Manager 3.4
The following procedure outlines the process for upgrading Red Hat Enterprise Virtualization Manager 3.3 to Red Hat Enterprise Virtualization Manager 3.4. This procedure assumes that the system on which the Manager is installed is subscribed to the entitlements for receiving Red Hat Enterprise Virtualization 3.3 packages at the start of the procedure.
Important
If the upgrade fails, the
engine-setup command will attempt to roll your Red Hat Enterprise Virtualization Manager installation back to its previous state. For this reason, the repositories required by Red Hat Enterprise Virtualization 3.3 must not be removed until after the upgrade is complete as outlined below. If the upgrade fails, detailed instructions display that explain how to restore your installation.
Procedure 15.6. Upgrading to Red Hat Enterprise Virtualization Manager 3.4
- Subscribe the system on which the Red Hat Enterprise Virtualization Manager is installed to the required entitlements for receiving Red Hat Enterprise Virtualization Manager 3.4 packages.
- With RHN Classic:
# rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.4
- With Subscription Manager:
# subscription-manager repos --enable=rhel-6-server-rhevm-3.4-rpms
- Update the base operating system:
# yum update
- Update the rhevm-setup package:
# yum update rhevm-setup
- Run the following command and follow the prompts to upgrade the Red Hat Enterprise Virtualization Manager:
# engine-setup
- Remove or disable the Red Hat Enterprise Virtualization Manager 3.3 repositories to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.3 packages.
- With RHN Classic:
# rhn-channel --remove --channel=rhel-x86_64-server-6-rhevm-3.3
- With Subscription Manager:
# subscription-manager repos --disable=rhel-6-server-rhevm-3.3-rpms