Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1234906

Summary:	Upgrade ovirt-hosted-engine-ha to 1.3.2
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	ovirt-hosted-engine-ha	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	alukiano, bmcclain, dfediuck, gklein, istein, juwu, lsurette, sbonazzo, ykaul
Target Milestone:	ovirt-3.6.0-rc	Keywords:	Rebase, Triaged
Target Release:	3.6.0	Flags:	nsednev: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-ha-1.3.0-0.1.alpha.git5f8c290.el7ev	Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:	Rebase package(s) to version: 1.3.2 See bugs in Depends On field.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-09 19:49:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1116469, 1150087, 1156596, 1164226, 1190071, 1229774, 1235591, 1248539, 1267511, 1268892, 1276650, 1276740
Bug Blocks:

Description Sandro Bonazzola 2015-06-23 13:21:19 UTC

Upgrade ovirt-hosted-engine-ha to 1.3.0

Comment 2 Nikolai Sednev 2015-10-20 13:39:05 UTC

Worked for me, while upgrading from ovirt-hosted-engine-ha-1.2.7.2-1.el7ev.noarch to ovirt-hosted-engine-ha-1.3.1-1.el7ev.noarch.

Comment 3 Simone Tiraboschi 2015-11-03 11:21:41 UTC

*** Bug 1277386 has been marked as a duplicate of this bug. ***

Comment 4 Nikolai Sednev 2015-12-20 09:33:28 UTC

Should we move this to ovirt-hosted-engine-ha-1.3.3.3-1.20151211131547.gitb84582e.el7.noarch ? Works for me there just fine.

Comment 5 Nikolai Sednev 2015-12-22 14:12:59 UTC

verified in 3.6.1.

Comment 7 errata-xmlrpc 2016-03-09 19:49:11 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0422.html