Bug 1071793 - RHEV-M fails to detect 'AMD Opteron G5' as CPU_Type for hypervisors.
Summary: RHEV-M fails to detect 'AMD Opteron G5' as CPU_Type for hypervisors.
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 3.3.2
Assignee: Arik
QA Contact: meital avital
Whiteboard: virt
Depends On: 1064880
TreeView+ depends on / blocked
Reported: 2014-03-03 07:45 UTC by Michal Skrivanek
Modified: 2019-04-28 09:26 UTC (History)
13 users (show)

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.
Clone Of: 1064880
Last Closed: 2014-04-09 17:56:13 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0384 0 normal SHIPPED_LIVE rhevm 3.3.2 bug fix update 2014-04-09 21:52:20 UTC
oVirt gerrit 24837 0 None None None Never
oVirt gerrit 24961 0 None None None Never
oVirt gerrit 24965 0 None None None Never

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:


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.


Note You need to log in before you can comment on or make changes to this bug.