Synopsis

ovirt-hosted-engine-setup bug fix and enhancement update

Type/Severity

Product Enhancement Advisory

Topic

Updated ovirt-hosted-engine-setup packages that fix several bugs and add various enhancements are now available.

Description

The ovirt-hosted-engine-setup package provides a self-hosted engine tool for Red Hat Virtualization Manager. A self-hosted engine is a virtualized environment in which the Manager runs on a virtual machine on the hosts managed by the Manager.

Changes to the ovirt-hosted-engine-setup component:

• Previously, when restoring a backup of a self-hosted engine on a different environment administrators were sometimes required to remove the previous self-hosted engine's storage domain and virtual machine. This was accomplished from within the engine's database, which was a risk-prone procedure. With this update, a new CLI option enables administrators to remove the previous self-hosted engine's storage domain and virtual machine directly from the backup of the engine during the restore procedure. (BZ#1240466)
  
• This update allows you to enable SSH access for the Manager virtual machine when deploying the self-hosted engine. You can choose between yes, no and without-password. You can also pass a public SSH key for the root user during deployment. (BZ#1331858)
  
• With this update, the user is now directed to the upgrade helper tool when performing appliance upgrades from ovirt-hosted-engine-setup. (BZ#1370041)
  
• Previously, the Red Hat Enterprise Virtualization 3.5 self-hosted engine storage domain upgrade failed on the initial host due to permissions errors. This has been corrected. (BZ#1401359)
  
• Previously, hosted-engine-setup and cockpit incorrectly accepted host addresses containing underscores. The Manager correctly refused the addresses. This meant that hosted-engine-setup would fail while trying to add the host to the Manager and the user had to cleanup and restart the installation. Now, the host address syntax is validated in hosted-engine-setup and hosted-engine-setup will refuse to deploy is the address syntax is invalid. (BZ#1366270)
  
• Previously, a self-hosted engine upgrade failed during engine-setup if the database backup file was not loaded from /root/ on the host. This has now been corrected. (BZ#1394740)

Solution

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

For details on how to apply this update, refer to:
https://access.redhat.com/articles/2974891

Affected Products

• Red Hat Virtualization 4 x86_64

Fixes

• BZ - 1240466 - Restoring self-hosted engine from backup has conflict between new and old HostedEngine VM
• BZ - 1331858 - [RFE] Allow user to enable ssh access for RHEV-M appliance during hosted-engine deploy
• BZ - 1366270 - hosted-engine-setup (and cockpit) accepts host address with an underscore while the engine correctly refuses them
• BZ - 1370041 - [Text] The HE upgrade tool should point users at the upgrade helper
• BZ - 1376114 - [TEXT][HE] Warn on addition of new HE host via host-deploy
• BZ - 1379405 - Build ovirt-hosted-engine-setup for RHEL 7 RHV 4.1
• BZ - 1394740 - Hosted Engine upgrade is failing during engine-setup if the db backup file is not in /root/
• BZ - 1420283 - Ensure that upgrading the engine vm from 3.6/el6 to 4.0/el7 is properly working once we release 4.1

CVEs

(none)

References

(none)

Red Hat Virtualization 4

SRPM
ovirt-hosted-engine-setup-2.1.0.5-1.el7ev.src.rpm	SHA-256: 16c40a53a553fcf3eff69f47b44b1328af84cfb00c4fca35433d1e5bcfb9695c
x86_64
ovirt-hosted-engine-setup-2.1.0.5-1.el7ev.noarch.rpm	SHA-256: d545dfb2dd7523b1e78b80fd0ab35ae030b16a7101999606fe230751711866e5