5.3. Updating the Manager Virtual Machine

To update a self-hosted engine from your current version of 4.2 to the latest version of 4.2, you must place the environment in global maintenance mode and then follow the standard procedure for updating between minor versions.

Enabling Global Maintenance Mode

You must place the self-hosted engine environment in global maintenance mode before performing any setup or upgrade tasks on the Manager virtual machine.

Procedure

  1. Log in to one of the self-hosted engine nodes and enable global maintenance mode: 

    # hosted-engine --set-maintenance --mode=global

  2. Confirm that the environment is in maintenance mode before proceeding: 

    # hosted-engine --vm-status

Updating the Red Hat Virtualization Manager

Updates to the Red Hat Virtualization Manager are released through the Content Delivery Network.

Procedure

  1. On the Red Hat Virtualization Manager machine, check if updated packages are available: 

    # engine-upgrade-check
    Note

    If updates are expected, but not available, enable the required repositories. See Enabling the Red Hat Virtualization Manager Repositories in the Installation Guide.

  2. Update the setup packages: 

    # yum update ovirt\*setup\*

  3. Update the Red Hat Virtualization Manager. The engine-setup script prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service. 

    # engine-setup
    Note

    The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and may not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup.

    Important

    The update process may take some time; allow time for the update process to complete and do not stop the process once initiated.

  4. Update the base operating system and any optional packages installed on the Manager: 

    # yum update
    Important

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

Disabling Global Maintenance Mode

Procedure

  1. Log in to one of the self-hosted engine nodes and disable global maintenance mode: 

    # hosted-engine --set-maintenance --mode=none

  2. Confirm that the environment is running: 

    # hosted-engine --vm-status