Bug 1034821

Summary: Hosted-setup asks for CPU type but it doesn't set cluster to that CPU Level
Product: Red Hat Enterprise Virtualization Manager Reporter: Pablo Iranzo Gómez <pablo.iranzo>
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: movciari
Severity: medium Docs Contact:
Priority: low    
Version: 3.3.0CC: dfediuck, didi, iheim, oschreib, pstehlik, scohen
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-hosted-engine-setup-1.0.0-2.el6ev Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 16:56:03 UTC Type: Bug
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:    
Bug Blocks: 1020228    

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