Bug 1034821 - Hosted-setup asks for CPU type but it doesn't set cluster to that CPU Level
Summary: Hosted-setup asks for CPU type but it doesn't set cluster to that CPU Level
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: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 3.3.0
Assignee: Sandro Bonazzola
QA Contact: movciari
URL:
Whiteboard: integration
Depends On:
Blocks: GSS_RHEV_33_BETA
TreeView+ depends on / blocked
 
Reported: 2013-11-26 14:54 UTC by Pablo Iranzo Gómez
Modified: 2014-01-21 16:56 UTC (History)
6 users (show)

Fixed In Version: ovirt-hosted-engine-setup-1.0.0-2.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:56:03 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:0083 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-setup 2014-01-21 21:42:22 UTC
oVirt gerrit 22129 0 None MERGED packaging: setup: set cluster level CPU id 2020-04-03 13:32:23 UTC
oVirt gerrit 22291 0 None MERGED packaging: setup: set cluster level CPU id 2020-04-03 13:32:22 UTC

Description Pablo Iranzo Gómez 2013-11-26 14:54:44 UTC 
Description of problem:

Hi
ovirt-hosted setup asks for CPU compatibility among the ones available, and it sets it correctly on the vm.conf file, but doesn't setup the cluster as expected.

Instead, it uses host max CPU level, avoiding newer hostst to become operational if they have lower CPU type.

This is not critical as you can later edit it, but IMHO, it should do it at setup time. (Also, on the correct datacenter cluster)
Comment 3 Sandro Bonazzola 2013-12-11 13:44:34 UTC 
patch merged on upstream master and 1.0 branches.
Comment 8 errata-xmlrpc 2014-01-21 16:56:03 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-0083.html
Note You need to log in before you can comment on or make changes to this bug.