Updating the Self-Hosted Engine

Important:

If you are upgrading your environment, refer to Updating engine or self-hosted engine to 4.4 in the Upgrading Your Environment to 4.5 section.

Before you can update your self-hosted engine, you must place the self-hosted engine environment in global maintenance mode.

Log into your self-hosted engine host and enable global maintenance mode.
```
# hosted-engine --set-maintenance --mode=global
```
Confirm that the environment is in maintenance mode .
```
# hosted-engine --vm-status
```
You should see the following message indicating that the cluster is in maintenance mode.
```
!! Cluster is in GLOBAL MAINTENANCE mode !!
```
Update the release rpm.
- If you are updating from 4.4 to the latest version of 4.4, run:
```
# dnf update oracle-ovirt-release-el8
```
- If you are updating from 4.5 to the latest version of 4.5, run:
```
# dnf update oracle-ovirt-release-45-el8
```
Log in to the engine virtual machine and check to see if your engine is eligible to update and if there are updates for any packages.
```
# engine-upgrade-check
...
Upgrade available.
```
Update the setup packages and resolve dependencies.
```
# dnf update ovirt\*setup\*
...
Complete!
```
Update the self-hosted engine:
```
# engine-setup
```
Important:
The update process might take some time. Do not stop the process before it completes.

The engine-setup script:
- Prompts you with some configuration questions
  
  For more information, see Engine Configuration Options in the Oracle Linux Virtualization Manager: Getting Started.
- Stops the ovirt-engine service
- Downloads and installs the updated packages
- Backs up and updates the database
- Performs post-installation configuration
- Starts the ovirt-engine service
Note:
The engine-setup script displays stored configuration values supplied during the initial engine installation process. These stored values display when previewing the configuration and may not be up to date if you ran engine-config after installation. However, engine-setup will not overwrite your updated values.
For example, if you ran engine-config to update SANWipeAfterDelete to true after installation, engine-setup outputs Default SAN wipe after delete: False in the configuration preview. However, engine-setup will not apply this value; rather, it will keep the SANWipeAfterDelete to true setting.

If the update is successful, you will see:
```
Execution of setup completed successfully
```
If the update fails, the engine-setup command attempts to rollback your installation to its previous state. If you encounter a failed update, detailed instructions display explaining how to restore your installation.
Update the base operating system and any optional packages installed on the engine.
```
# dnf update
```
Important:
If any core libraries or services were upgraded, reboot the system to complete the changes. Run the following command to confirm a reboot is required: dnf needs-restarting -r,

After you update your self-hosted engine, you must disable global maintenance mode for the self-hosted engine environment.

Log in to the engine virtual machine and shut it down.
Log in to the self-hosted engine host and disable global maintenance mode.
```
# hosted-engine --set-maintenance --mode=none
```
Note:

When you exit global maintenance mode, ovirt-ha-agent starts the engine virtual machine, and then the engine automatically starts. This process can take up to ten minutes.
Confirm that the environment is running.
```
# hosted-engine --vm-status
```
The status information shows Engine Status and its value should be:
```
{"health": "good", "vm": "up", "detail": "Up"}
```
When the virtual machine is still booting and the engine hasn’t started yet, the Engine status is:
```
{"reason": "bad vm status", "health": "bad", "vm": "up", "detail": "Powering up"}
```
If this happens, wait a few minutes and try again.