15.8. Updating a Self-Hosted Engine

Procedure

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

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

   Copy to Clipboard Toggle word wrap

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

   # hosted-engine --vm-status

   Copy to Clipboard Toggle word wrap

   You should see a message indicating that the cluster is in maintenance mode.

Procedure

1. Log in to the Manager virtual machine.

2. Check if updated packages are available:

   # engine-upgrade-check

   Copy to Clipboard Toggle word wrap

3. Update the setup packages:

   # yum update ovirt\*setup\* rh\*vm-setup-plugins

   Copy to Clipboard Toggle word wrap

4. Update the Red Hat Virtualization Manager with the engine-setup script. 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

   Copy to Clipboard Toggle word wrap

   When the script completes successfully, the following message appears:

   Execution of setup completed successfully

   Copy to Clipboard Toggle word wrap
   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 might 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 might take some time. Do not stop the process before it completes.

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

   # yum update

   Copy to Clipboard Toggle word wrap
   Important

   If any kernel packages were updated:

   1. Disable global maintenance mode
   2. Reboot the machine to complete the update.

Procedure

1. Log in to the Manager virtual machine and shut it down.

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

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

   Copy to Clipboard Toggle word wrap

   When you exit global maintenance mode, ovirt-ha-agent starts the Manager virtual machine, and then the Manager automatically starts. It can take up to ten minutes for the Manager to start.

3. Confirm that the environment is running:

   # hosted-engine --vm-status

   Copy to Clipboard Toggle word wrap

   The listed information includes Engine Status. The value for Engine status should be:

   {"health": "good", "vm": "up", "detail": "Up"}

   Copy to Clipboard Toggle word wrap
   Note

   When the virtual machine is still booting and the Manager hasn’t started yet, the Engine status is:

   {"reason": "bad vm status", "health": "bad", "vm": "up", "detail": "Powering up"}

   Copy to Clipboard Toggle word wrap

   If this happens, wait a few minutes and try again.