Bug 1092378

Summary:	hosted-engine script fails with Traceback when cluster doesn't return a CPU type
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-hosted-engine-setup	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	aburden, acathrow, adahms, amureini, ayersmj, bazulay, didi, dougsland, iheim, juan.hernandez, lveyde, pstehlik, Rhev-m-bugs, sbonazzo, scohen, stirabos, ukar, yeylon
Target Milestone:	---	Keywords:	Reopened, ZStream
Target Release:	3.3.3
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:	ovirt-hosted-engine-setup-1.0.0-9.el6ev.noarch.rpm	Doc Type:	Bug Fix
Doc Text:	Previously, the Red Hat Enterprise Virtualization Manager would not provide CPU information for cluster objects in the response to the first query made by the ovirt-hosted-engine-setup command under certain conditions. This would cause setup to fail after timing out due to not having CPU information. Now, the ovirt-hosted-engine-setup command queries the Red Hat Enterprise Virtualization Manager again until the timeout is reached, allowing CPU information to be retrieved corrected and setup to complete successfully.	Story Points:	---
Clone Of:	1088572	Environment:
Last Closed:	2014-05-27 08:57:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1088572
Bug Blocks:

Comment 3 Andrew Burden 2014-05-02 05:57:18 UTC

Hey Team,

I'm writing up the errata for RHBA-2014:17611-01 but I can't figure out what the fix was. Can you please help me by filling out the remaining Doc Text?

Cheers

Comment 4 Artyom 2014-05-04 07:37:58 UTC

Verified on is36

Comment 6 errata-xmlrpc 2014-05-27 08:57:45 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.

http://rhn.redhat.com/errata/RHBA-2014-0546.html