Bug 866492

Summary: [rhevm-dwh] - Duplicate rows in Views
Product: Red Hat Enterprise Virtualization Manager Reporter: David Botzer <dbotzer>
Component: ovirt-engine-dwhAssignee: Yaniv Lavi <ylavi>
Status: CLOSED ERRATA QA Contact: David Botzer <dbotzer>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: bazulay, dyasny, iheim, italkohe, pstehlik, Rhev-m-bugs, sgrinber, thildred, ykaul
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: si22 - rhevm-dwh-3.1.0-16.el6ev.noarch.rpm Doc Type: Bug Fix
Doc Text:
Previously, the virtual machine hourly history view and the virtual machine daily history view in the engine database contained duplicated records with the same history identifiers. Duplicated history identifiers distort historical data. The views were corrected so that each entry has a unique history identifier. The statistics contained in the views are no longer prone to distortion caused by duplicated history identifiers.
Story Points: ---
Clone Of:
: 868937 (view as bug list) Environment:
Last Closed: 2012-12-04 18:20:41 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:    
Bug Blocks: 868937    
Attachments:
Description Flags
duplicate none

Description David Botzer 2012-10-15 13:44:37 UTC
Created attachment 627441 [details]
duplicate

Description of problem:
When displaying the views in history db, I see duplicate records with the same history ID

Version-Release number of selected component (if applicable):
3.1/si20

How reproducible:
always

Steps to Reproduce:
1.install rhevm+reports+dwh
2.create several VMs and run for couple of days
3.check the vm_hourly_history_view & v3_1_vm_daily_history_view
  
Actual results:
Duplicate rows with same values

Expected results:
should have unique rows per history id

Additional info:

Comment 3 David Botzer 2012-10-16 11:33:02 UTC
Hi Yaniv,

Why is this blocker ?
How does it affect Reports ?

Comment 4 Yaniv Lavi 2012-10-17 14:08:14 UTC
(In reply to comment #3)
> Hi Yaniv,
> 
> Why is this blocker ?
> How does it affect Reports ?

displays duplicate data and causes distortion is stats.

Comment 5 Yaniv Lavi 2012-10-21 14:10:40 UTC
Added bug on talend:
https://jira.talendforge.org/browse/TDI-23367

And workaround patch:
http://gerrit.ovirt.org/8702



Yaniv

Comment 6 Yaniv Lavi 2012-10-22 12:23:50 UTC
Changed in patch upstream:
http://gerrit.ovirt.org/#/c/8702/

and downstream:
https://gerrit.eng.lab.tlv.redhat.com/#/c/2781/


Yaniv

Comment 9 David Botzer 2012-10-25 06:00:47 UTC
Not Fixed, 3.1/si22.1
clean installation of si22 & si22.1, One entity of a kind ran for 24H

v3_1_vm_hourly_history_view

16;"2012-10-25 05:00:00+02"
16;"2012-10-25 05:00:00+02"
15;"2012-10-25 04:00:00+02"
15;"2012-10-25 04:00:00+02"

See pic

Not Fixed, 3.1/si22.1

Comment 10 David Botzer 2012-10-25 06:04:18 UTC
Not Fixed, 3.1/si22.1
clean installation of si22 & si22.1, One entity of a kind ran for 24H

v3_1_vm_hourly_history_view

16;"2012-10-25 05:00:00+02"
16;"2012-10-25 05:00:00+02"
15;"2012-10-25 04:00:00+02"
15;"2012-10-25 04:00:00+02"

See pic

Not Fixed, 3.1/si22.1

Comment 11 Yaniv Lavi 2012-10-25 14:04:40 UTC
Needed to do another fix:
upstream - http://gerrit.ovirt.org/#/c/8824/
downstream - https://gerrit.eng.lab.tlv.redhat.com/#/c/2879/



Yaniv

Comment 12 David Botzer 2012-11-08 08:36:18 UTC
Fixed, 3.1/si24 (remote, Local, Clean & Upgraded)
No Dupicates in history db views:
v3_1_vm_hourly_history_view
v3_1_vm_daily_history_view
v3_1_vm_interface_hourly_history_view
v3_1_vm_interface_daily_history_view
v3_1_vm_disk_hourly_history_view
v3_1_vm_disk_daily_history_view
Fixed, 3.1/si24 (remote, Local, Clean & Upgraded)

Same as bz Bug 843468 - 3.0.z - [rhevm-dwh] - History DB - Duplicate records in History Aggregation Views

Comment 14 errata-xmlrpc 2012-12-04 18:20:41 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-2012-1534.html