Red Hat Bugzilla – Bug 892596
engine- No Statisitics for Disk Read/Write in Views (v3_2 & v3_1) vm_disk_samples_history_view (hence no statistics in DWH)
Last modified: 2016-02-10 11:38:11 EST
Created attachment 673922 [details]
Description of problem:
No Statisitics for Disk Read/Write in Views (v3_2 & v3_1) vm_disk_samples_history_view (if there is no data in samples it affects both hours & days)
This applies for both DC's versions 3.1 & 3.2 on rhevm 3.2
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Installrhevm+dwh+reports on RHEL64 Hosts
2.Create DC 3.1 or 3.2 with 1 host
3.Create 1VM Winxp from template or new with IOLoadGenerator
4.run IOLoadGenerator.exe -f iozone/iozone.exe
Data is not saved in the correct tables/views for vm_disk_samples_history
Should save & display the Read/Write data
Created attachment 673923 [details]
Data is also missing from:
Yes, added regression in keyword
DWH gather data correctly where engine has NULL in Read/Write,
Engine View is dwh_vm_disks_history_view
Adding storage keyword, looks like we are missing some statistics report.
Reproduced on 3.2/SF5
(In reply to comment #10)
> Reproduced on 3.2/SF5
David, why are you testing this?
The bug is in "ASSIGNED" status - it was never fixed.
As a response to Vered
This bug is marked as REGRESSION - when was was the last time that it worked? (3.1? 3.0?)
According to Yaniv Dary the actual select query creating dwh_vm_disks_history_view returns no records, which means this is not a reports/dwh issue and can be fixed on the engine alone. I.e., no need for winXP/dwh/reports installations.
We expect to see data on disks of currently running VMs in the system.
Same as Vered, Issue is at the engine DB
(In reply to comment #15)
> Same as Vered, Issue is at the engine DB
This is not the question.
I ask again:
In what version was this last confirmed to work?
The Disk IO stats were working at 3.0/ic138.1
Same issue as the this BZ was Also reported
In 891322 - 3.1/si24
disk_image_dynamic table does not gather statistics, hence related dwh views are empty.
3.1 introduced DiskImage entity to the system, separating (engine) image group and image id (or image and volume in vdsm, respectively). The data received from vdsm is (correctly so) for image group, while the data in the table is updated by image id (volume). Hence no data is actually updated.
Is this BZ fixed for 3.2/sf13 ?
(In reply to comment #21)
> Hi Vered,
> Is this BZ fixed for 3.2/sf13 ?
Yep, see external tracker for more info.
History DB has data in all 3 views
samples/hours/daily - VM_DISK_Read/Write
3.2 has been released