Bug 1373636

Summary:	CPU Types does not match list documented for RHV 4.0
Product:	Red Hat Quickstart Cloud Installer	Reporter:	James Olin Oden <joden>
Component:	Installation - RHEV	Assignee:	Derek Whatley <dwhatley>
Status:	CLOSED ERRATA	QA Contact:	James Olin Oden <joden>
Severity:	medium	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.0	CC:	bthurber, jesusr, smallamp, tsanders
Target Milestone:	---	Keywords:	Triaged
Target Release:	1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-28 01:39:20 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:

Description James Olin Oden 2016-09-06 20:03:26 UTC

Description of problem:
The RHV 4.0 documentation list of supported CPU Types is here:

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/technical-reference#Hypervisor_Requirements

And the QCI list is missing:

- AMD Opteron G4
- AMD Opteron G5
- IBM Power 8     

And it has one that is not listed as supported:

- Broadwell

Version-Release number of selected component (if applicable):
QCI-1.0-RHEL-7-20160902.5

How reproducible:
Always

Steps to Reproduce:
1.  Do a RHV deployment and get to the RHV - Configuration Screen
2.  Look a the CPU Type's in the CPU Type dropdown
3.  Compare them to the docs here:  

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/technical-reference#Hypervisor_Requirements

Actual results:

They do not match exactly.

Expected results:

They should match.

Comment 4 Derek Whatley 2016-09-08 13:34:55 UTC

PR posted https://github.com/fusor/fusor/pull/1214

Comment 5 James Olin Oden 2016-10-11 18:10:09 UTC

Verified in QCI-1.1-RHEL-7-20161007.t.0

Comment 8 errata-xmlrpc 2017-02-28 01:39:20 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.

https://access.redhat.com/errata/RHEA-2017:0335