- Issued:
- 2015-04-28
- Updated:
- 2015-04-28
RHBA-2015:0910 - Bug Fix Advisory
Synopsis
ovirt-hosted-engine-setup bug fix update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated ovirt-hosted-engine-setup packages that fix several bugs are now
available.
Description
Changes to the ovirt-hosted-engine-setup component:
The ovirt-hosted-engine-setup packages have been upgraded to upstream version
1.2.5, which provides several bug fixes over the previous version. (BZ#1192937)
- Previously, when attempting to deploy a hosted engine using iSCSI storage, and
the nominated LUN contained a master storage domain from a previous setup, the
deployment would fail because it would not validate the storage domain. Now, the
handling of the existing storage domain has been improved so that deployment of
a hosted engine does not fail because the LUN contains a storage domain from a
previous setup. (BZ#1190636)
- Previously, hosts were hardcoded to overwrite the iptables rules when the host
was added using the 'hosted-engine --deploy' command, even if the user answered
'No' to the question 'iptables was detected on your computer, do you wish setup
to configure it?'. Now, the host is not hardcoded and an answer of 'No' to this
question is recognized by both the 'hosted-engine --deploy' configuration as
well as during the request to the engine to add the host. Therefore answering
'No' prevents the existing iptables rules from being overwritten on the host.
(BZ#1192462)
- Previously, when attempting to deploy a hosted engine using iSCSI storage, and
the nominated LUN contained a master storage domain from a previous setup, the
deployment would fail because it would not validate the storage domain. Now, the
handling of the existing storage domain has been improved so that deployment of
a hosted engine does not fail because the LUN contains a storage domain from a
previous setup. (BZ#1199905)
- Previously, the hosted engine would check to ensure an ISO image was readable
by the VDSM user but not necessarily the KVM user. This meant it was possible
for the virtual machine to be unable to boot from the ISO even if though it
passed the check. Now, this check has been expanded and, if the ISO image
passes, the virtual machine can boot from it as expected. (BZ#1181585)
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/articles/11258
Affected Products
- Red Hat Virtualization 3.5 x86_64
- Red Hat Virtualization 3 for RHEL 7 x86_64
Fixes
- BZ - 1181585 - [hosted-engine] Bad check of iso image permission
- BZ - 1190636 - [hosted-engine] [iSCSI support] connectStoragePools fails with "SSLError: The read operation timed out" while adding a new host to the setup
- BZ - 1192462 - [RFE][HC] make override of iptables configurable when using hosted-engine
- BZ - 1192937 - Rebase ovirt-hosted-engine-setup to upstream 1.2.2
- BZ - 1199905 - [hosted-engine][iscsi] [dirty storage] [ ERROR ] Failed to execute stage 'Misc configuration': Wrong Master domain or its version:
- BZ - 1207062 - [hosted-engine] Deployment fails with "The VDSM host was found in a failed state. Please check engine and bootstrap installation logs."
CVEs
(none)
References
(none)
Red Hat Virtualization 3.5
SRPM | |
---|---|
ovirt-hosted-engine-setup-1.2.2-3.el6ev.src.rpm | SHA-256: 565c6907003ca74019bc88b42a00928b68611b4012a55b416604c7d65de7df54 |
x86_64 | |
ovirt-hosted-engine-setup-1.2.2-3.el6ev.noarch.rpm | SHA-256: 49a56a5e5e45183657fb5f83a02e82d5aacc4fde4b28f328325b29ec7070aee1 |
Red Hat Virtualization 3 for RHEL 7
SRPM | |
---|---|
x86_64 | |
ovirt-hosted-engine-setup-1.2.2-3.el7.noarch.rpm | SHA-256: 2de934e913e4787e9ddfbd45dfbe8f5592db9fdecd69986425a182f681035bbd |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.