RHEA-2014:0080 - Product Enhancement Advisory

Topic

A new ovirt-hosted-engine-ha package is now available.

Description

The ovirt-hosted-engine-ha package enables the self-hosted engine to be highly
available. A self-hosted engine is a virtualized environment in which the Red
Hat Enterprise Virtualization Manager runs on a virtual machine on the hosts
managed by the Manager. If the host running the virtual machine goes into
maintenance, the virtual machine is migrated automatically to another host in
the environment.

To install the self-hosted engine, run:
# yum install ovirt-hosted-engine-setup

Refer to the Red Hat Enterprise Virtualization 3.3 Installation Guide for
further information.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html-single/Installation_Guide/index.html#chap-Self-Hosted_Engine

All Red Hat Enterprise Virtualization Manager users should install this update
which includes this enhancement.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/site/articles/11258

Affected Products

• Red Hat Virtualization 3.3 x86_64

Fixes

• BZ - 999456 - NewPkg: Add ovirt-hosted-engine-ha
• BZ - 1008505 - ha broker service should check if metadate file exist upon starting. if not exist should give a warning message and fail to start.
• BZ - 1013563 - Error while monitoring engine: Could not start sanlock because of wrong service path in sudoers file
• BZ - 1013638 - when the HA agent detects that the vm died unexpectedly, it should call --vm-poweroff before --vm-start
• BZ - 1014112 - Missing parameter to log message which is printed when a vm needs to be migrated to a better host causes the migration failure.
• BZ - 1014241 - Sometimes OS will cache the data from nfs mounts which will cause to host take not updated meta data.
• BZ - 1015721 - Migration fails due to bad call to vdsm api
• BZ - 1015724 - Add maintenance mode to hosted engine agent
• BZ - 1017406 - HA Agent should use startMonitoringDomain VDSM API for monitoring hosted engine storage domain
• BZ - 1018278 - Packaging errors in HA Agent
• BZ - 1018829 - broker started ~200ms after agent causing the transient error.
• BZ - 1018849 - TImeout for monitor domain should be raised.
• BZ - 1019468 - ha agent don't handle vm status 'Waiting for Launch'.
• BZ - 1019471 - ha agent log files rotate frequency should be changed.
• BZ - 1021064 - Distribute doc directory contents in source tarball
• BZ - 1023965 - HA agent might fail to work correctly due to incorrect path to the Gluster storage domain.
• BZ - 1026351 - hosted-engine --vm-status reports about hosts that not participating in HA anymore.
• BZ - 1026377 - HA agent dies after manual migration of engine vm.
• BZ - 1032644 - hosted engine email notifications cause email flood.
• BZ - 1032667 - ha broker floods vdsm.log file
• BZ - 1034205 - Migrate engine VM due to excessive CPU load
• BZ - 1034321 - missing maintenance information when running hosted-engine --vm-status
• BZ - 1034787 - [RFE] Hosted-HA should not start infinite reboot loop when VDSM reports the engine VM as "Running"
• BZ - 1036710 - HA agent should behave appropriately when newer metadata is encountered
• BZ - 1037654 - Factors comprising host score should be configurable
• BZ - 1039614 - Migrate VM only for local maintenance

CVEs

(none)

References

(none)