6.3. Upgrading to Red Hat Enterprise Virtualization Manager 3.3
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.2 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 6.1. Upgrading to Red Hat Enterprise Virtualization Manager 3.3
- Subscribe the system to the required entitlements for receiving Red Hat Enterprise Virtualization Manager 3.3 packages.Subscription Manager
Red Hat Enterprise Virtualization 3.3 packages are provided by the
rhel-6-server-rhevm-3.3-rpms
repository associated with theRed Hat Enterprise Virtualization
entitlement. Use thesubscription-manager
command to enable the repository in youryum
configuration.# subscription-manager repos --enable=rhel-6-server-rhevm-3.3-rpms
Red Hat Network ClassicThe Red Hat Enterprise Virtualization 3.3 packages are provided by the
Red Hat Enterprise Virtualization Manager (v.3.3 x86_64)
channel. Use therhn-channel
command or the Red Hat Network web interface to subscribe to theRed Hat Enterprise Virtualization Manager (v.3.3 x86_64)
channel:# rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.3
- Update the base operating system:
# yum update
In particular, if you are using the JBoss Application Server from JBoss Enterprise Application Platform 6.0.1, you must run the above command to upgrade to Enterprise Application Platform 6.1. - Update the rhevm-setup package to ensure you have the most recent version of
engine-setup
.# yum update rhevm-setup
- Run the
engine-setup
command and follow the prompts to upgrade Red Hat Enterprise Virtualization Manager.# engine-setup [ INFO ] Stage: Initializing Welcome to the RHEV 3.3.0 upgrade. Please read the following knowledge article for known issues and updated instructions before proceeding with the upgrade. RHEV 3.3.0 Upgrade Guide: Tips, Considerations and Roll-back Issues https://access.redhat.com/articles/408623 Would you like to continue with the upgrade? (Yes, No) [Yes]:
- Remove Red Hat Enterprise Virtualization Manager 3.2 repositories to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.2 packages.Subscription Manager
Use the
subscription-manager
command to disable the Red Hat Enterprise Virtualization 3.2 repository in youryum
configuration.# subscription-manager repos --disable=rhel-6-server-rhevm-3.2-rpms
Red Hat Network ClassicUse the
rhn-channel
command or the Red Hat Network web interface to remove theRed Hat Enterprise Virtualization Manager (v.3.2 x86_64)
channels.# rhn-channel --remove --channel=rhel-x86_64-server-6-rhevm-3.2
- Ensure all of your virtualization hosts are up to date and running the most recent Red Hat Enterprise Linux packages or Hypervisor images.
- Change all of your clusters to use compatibility version 3.3.
- Change all of your data centers to use compatibility version 3.3.