Bug 973266

Summary:	[rhevm-dwh] - enum_translator table - missing enum_key '20' & '21' for OS_TYPE (DB ovirt_engine_history)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Idith Tal-Kohen <italkohe>
Component:	ovirt-engine-dwh	Assignee:	Yaniv Lavi <ylavi>
Status:	CLOSED ERRATA	QA Contact:	David Botzer <dbotzer>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, bazulay, cpelland, dbotzer, iheim, jkt, pstehlik, Rhev-m-bugs, sgrinber, thildred, ylavi
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	SF18 - rhevm-dwh-3.2.1-1.el6ev.noarch.rpm	Doc Type:	Bug Fix
Doc Text:	Previously, the engine history database did not include ENUM value translators for Windows 8 and Windows Server 2012. Without those translators, reports on virtual machines by operating system did not include information about virtual machines running either of Windows 8 or Windows Server 2012. ENUM value translators were added to the engine history database for Windows 8 and Windows Server 2012, and now virtual machines running either operating system are included in reports by operating system.	Story Points:	---
Clone Of:	966437	Environment:
Last Closed:	2013-07-16 13:28:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	966437
Bug Blocks:

Comment 2 David Botzer 2013-06-16 14:58:54 UTC

Yaniv,
SF18 - rhevm-dwh-3.2.1-1.el6ev.noarch.rpm

I have installed SF18, but DWH is - rhevm-dwh-3.2.0-10.el6ev.noarch

Please advise,

Comment 3 David Botzer 2013-06-17 08:29:05 UTC

rhevm-dwh-3.2.1-1.el6ev.noarch.rpm is not included in SF18

Comment 4 David Botzer 2013-06-20 10:49:09 UTC

Fixed, 3.2/sf18
I see 20,21,23
Fixed, 3.2/sf18

If needed 22, i will open bz

Comment 6 errata-xmlrpc 2013-07-16 13:28:11 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-2013-1075.html