Bug 1092378 - hosted-engine script fails with Traceback when cluster doesn't return a CPU type
Summary: hosted-engine script fails with Traceback when cluster doesn't return a CPU type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-setup
Version: 3.3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: 3.3.3
Assignee: Sandro Bonazzola
QA Contact: Artyom
URL:
Whiteboard: integration
Depends On: 1088572
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-29 08:01 UTC by rhev-integ
Modified: 2019-04-28 09:31 UTC (History)
18 users (show)

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.
Clone Of: 1088572
Environment:
Last Closed: 2014-05-27 08:57:45 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0546 0 normal SHIPPED_LIVE ovirt-hosted-engine-setup bug fix update 2014-05-27 12:56:57 UTC
oVirt gerrit 26887 0 master ABANDONED packaging: setup: avoid traceback on adding host Never
oVirt gerrit 26964 0 master MERGED packaging: setup: query cluster on attempts loop Never
oVirt gerrit 26965 0 ovirt-hosted-engine-setup-1.0 ABANDONED packaging: setup: query cluster on attempts loop Never
oVirt gerrit 26966 0 ovirt-hosted-engine-setup-1.1 MERGED packaging: setup: query cluster on attempts loop Never

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


Note You need to log in before you can comment on or make changes to this bug.