Bug 2014888
Summary: | oVirt executive dashboard/Virtual Machine dashboard does not actually show disk I/O operations per second, but it shows sum of I/o operations since the boot time of VM | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Abhishekh Patil <abpatil> |
Component: | ovirt-engine-dwh | Assignee: | Aviv Litman <alitman> |
Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4.8 | CC: | alitman, emarcus, gdeolive, klaas, lsurette, mavital, mhicks, mperina, srevivo |
Target Milestone: | ovirt-4.5.0 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-dwh-4.5.1 | Doc Type: | Bug Fix |
Doc Text: |
Dashboard field descriptions have been updated to match the real meanings of I/O operations data fields.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-26 16:23:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Metrics | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2010903 | ||
Bug Blocks: |
Description
Abhishekh Patil
2021-10-17 17:47:45 UTC
I think this is filed against the wrong component. I am guessing this should be filed against vdsm or whoever writes the v4_4_statistics_vms_disks_resources_usage_samples table. read_rate_bytes_per_second is correct, read_ops_per_second is a sum, not an average per second, same for write Verified in ovirt-engine-4.5.0.6-0.7.el8ev.noarch ovirt-engine-dwh-4.5.2-1.el8ev.noarch Second part of bug 2010903 In oVirt Executive Dashboards / 05 Virtual Machine Dashboard panel "Disk I/O operations since VM start (over time) (EX05-18)" has been renamed to say "since VM start" instead of previous "per second" which was incorrect. 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 (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4711 Due to QE capacity, we are not going to cover this issue in our automation |