Bug 1263797

Summary:	Cluster CPU Type in RHEV set to different value than specified in deployment configuration during wizard
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Matt Reid <mreid>
Component:	Installation - RHEV	Assignee:	Dylan Murray <dymurray>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	unspecified	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	high
Version:	1.0	CC:	apagac, arubin, bthurber, jmatthew, nperic, smallamp, tpapaioa
Target Milestone:	TP2	Keywords:	Triaged
Target Release:	1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-03 19:21:17 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:	1291836
Bug Blocks:	1271370

Description Matt Reid 2015-09-16 17:52:37 UTC

Description of problem:
During our deployment configuration, we set the CPU Type to Intel Nehalem, which is what our blades have for a CPU. Once everything had been deployed, the Cluster CPU Type that we can see in RHEV is set to Intel Westmere Family, which is a generation older than what we specified. 

Is that where we should see Nehalem set, or am I looking in the wrong spot? I don't see any other mention of CPU types in RHEV. I would expect the Cluster CPU Type to be Nehalem, not Westmere.

Version-Release number of selected component (if applicable):
Tech Preview


Additional info:

Comment 1 Stephen Herr 2015-10-28 21:36:40 UTC

Note to self:
The problem appears to be that the cpu_type option does nothing unless you are created the cluster, aka have changed the name to something other than "Default".
https://github.com/fusor/puppet-ovirt/blob/master/templates/dc_config.erb#L84=L94

We need to either update the puppet module to change the cpu_type on the cluster if it already exists (preferable), or have the UI force the user to change the cluster name if they set cpu_type if we can't do that.

Comment 2 Stephen Herr 2015-10-29 13:20:54 UTC

This should be fixed by https://github.com/fusor/puppet-ovirt/pull/3

Comment 3 John Matthews 2015-11-02 16:52:53 UTC

Included in: ruby193-rubygem-fusor_server-0.0.1-70.el7

Comment 4 Antonin Pagac 2016-01-11 13:48:23 UTC

I tried this by leaving DataCenter and Cluster names 'Default' and setting the processor type to Nehalem family in the RHCI UI, completely disregarding the processor family my host in fact has. The installed RHEV now shows cluster CPU type 'Intel SandyBridge family', which is not what I configured in the RHCI UI. I can see the Nehalem type configured on the Installation Review page. 
I then checked actual processor type on my hosts, and to the best of my and wiki knowledge it belongs to the Westmere family.

To summarize:
1. The actual cluster CPU type in RHEVM (SandyBridge) is not what I configured in RHCI UI (Nehalem)
2. The actual cluster CPU type in RHEVM (SandyBridge) is not the type of processor on the host machine (Westmere)

Version-Release number of selected component (if applicable):
ruby193-rubygem-fusor_server-0.0.1-85.el7.noarch
RHCI-6.0-RHEL-7-20160107.t.1-RHCI-x86_64-dvd1.iso

Comment 6 Dylan Murray 2016-01-21 13:53:52 UTC

Noticed an issue where the CPU type may still not be set if there is no assigned parameter on the cluster. Investigating this behavior and will update the bug accordingly.

Comment 8 John Matthews 2016-01-22 20:21:11 UTC

Compose of 1/22/16

Comment 9 Tasos Papaioannou 2016-01-28 14:53:15 UTC

Verified on RHCI-6.0-RHEL-7-20160125.t.0.