Bug 1071793

Summary: RHEV-M fails to detect 'AMD Opteron G5' as CPU_Type for hypervisors.
Product: Red Hat Enterprise Virtualization Manager Reporter: Michal Skrivanek <michal.skrivanek>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: acathrow, ahadas, iheim, lbopf, lpeer, mavital, michal.skrivanek, ofrenkel, pmukhedk, Rhev-m-bugs, sbonazzo, sherold, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 3.3.2   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: is35 Doc Type: Bug Fix
Doc Text:
Previously, a host with AMD Opterom Processor G5 was wrongly identified and set by the Red Hat Enterprise Virtualization Manager as 'AMD Opterom_G4'. Now, the CPU flags in the Manager have been altered to detect processor model AMD Opterom G5, and the Manger correctly detects when a host has AMD Opterom G5.
Story Points: ---
Clone Of: 1064880 Environment:
Last Closed: 2014-04-09 17:56:13 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: 1064880    
Bug Blocks:    

Comment 2 meital avital 2014-03-19 11:50:21 UTC
Customer verified, Please see bug #1064880

Comment 3 Zac Dover 2014-04-03 02:26:05 UTC
This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 5 errata-xmlrpc 2014-04-09 17:56:13 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-0384.html