Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 876074

Summary: [rhevm-dwh] - vm_disk_id is different between tables (v3_0_vm_disk_history_view & v3_1_vm_disk_history_view)
Product: Red Hat Enterprise Virtualization Manager Reporter: David Botzer <dbotzer>
Component: ovirt-engine-dwhAssignee: Yaniv Lavi <ylavi>
Status: CLOSED NOTABUG QA Contact: David Botzer <dbotzer>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: dyasny, iheim, pstehlik, Rhev-m-bugs, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-13 09:24:28 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:
Attachments:
Description Flags
diff-disk
none
remote-setup none

Description David Botzer 2012-11-13 09:21:39 UTC 
Created attachment 644009 [details]
diff-disk

Description of problem:
Reports BR10A, 10B, 10C doesnt display charts "Resource Usage of VM -> Top 5 busiest Disk Usage" correctly

as a result of vm_disk_id is different between tables (v3_0_vm_disk_history_view & v3_1_vm_disk_history_view)

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

How reproducible:
Always

Steps to Reproduce:
1.Create setup rhevm+dwh+reports and 1 VM
2.Verify the VM ID & disk ID 
v3_0_vm_disk_history_view & v3_1_vm_disk_history_view) (samples/Hourly/Daily)
  -Find correlation in in table "disks_vm_map"-> shows VM_ID & its Disk_ID
  
Actual results:
vm_disk_id is different between tables (v3_0_vm_disk_history_view & v3_1_vm_disk_history_view)

Expected results:
Should be the same & Reports 10A,10B,10C should display IO data for VM

Additional info:
the setups I tested were upgraded from si22/si23 to si24/si24.1
Comment 1 David Botzer 2012-11-13 09:23:19 UTC 
Created attachment 644010 [details]
remote-setup
Comment 2 Yaniv Lavi 2012-11-13 09:24:28 UTC 
This is not a bug.
This is in order to preserve the 3.0 API.
We moved from image_id to disk_id.


Yaniv