4.2. Upgrading the Manager from 4.1 to 4.2

Upgrade the Red Hat Virtualization Manager from 4.1 to 4.2.

Important

If the upgrade fails, the engine-setup command will attempt to roll your Red Hat Virtualization Manager installation back to its previous state. For this reason, the previous version’s repositories must not be removed until after the upgrade is complete. If the upgrade fails, detailed instructions display that explain how to restore your installation.

Procedure

  1. Enable the Red Hat Virtualization Manager 4.2, Red Hat Virtualization Tools, and Ansible Engine repositories: 

    # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms
# subscription-manager repos --enable=rhel-7-server-rhv-4-manager-tools-rpms
# subscription-manager repos --enable=rhel-7-server-ansible-2-rpms
    Important

    Red Hat Virtualization Manager 4.2 requires Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.1 to be installed on the Manager machine. Ensure that the jb-eap-7-for-rhel-7-server-rpms repository is enabled, and that the jb-eap-7.0-for-rhel-7-server-rpms repository is disabled. Run subscription-manager repos --list to check which repositories are enabled.

  2. Update the setup packages: 

    # yum update ovirt\*setup\*

  3. Run engine-setup and follow the prompts to upgrade the Red Hat Virtualization Manager: 

    # engine-setup

  4. Remove or disable the Red Hat Virtualization Manager 4.1 repositories to ensure the system does not use any 4.1 packages: 

    # subscription-manager repos --disable=rhel-7-server-rhv-4.1-rpms
# subscription-manager repos --disable=rhel-7-server-rhv-4.1-manager-rpms
# subscription-manager repos --disable=rhel-7-server-rhv-4-tools-rpms

  5. Update the base operating system: 

    # yum update
    Important

    If any kernel packages were updated, reboot the system to complete the update.

You can now update the hosts.