Description of problem: CloudForms correctly shows graphs of CPU, RAM, Network I/O, number of host, But Disk I/O is empty This is with respect to RHV clusters and not VMs Version-Release number of selected component (if applicable): 5.9.4.7 How reproducible: Always Steps to Reproduce: 1. Add RHV provider 2. Enable C & U collection 3. Compute>Infrastructure>Cluster>"Select RHV cluster" > Monitoring button> Utilization Actual results: Disk I/O graph is empty Expected results: Disk I/O graph should show data Additional info:
Created attachment 1517050 [details] Image showing the graphs after C&U for Cluster
Created attachment 1517051 [details] Image showing the graphs after C&U for Hosts
Another CU is also facing the same issue with Clusters as well as Hosts. Whenever the utilization of any Host or Cluster in RHEV is checked, It does not load the following graphs : - Virtual Machine CPU State - Disk IO - Network IO I am also attaching the screenshots for the same. Is there any update for this issue ?
Apparently we dealt with this before: https://bugzilla.redhat.com/show_bug.cgi?id=1424589 The Disk I/O is not actually collected from DWH. The attempt to do that was closed as deferred, since it will be collected to the Metrics Store. So to actually solve this it seems we would need to do one of two things: 1) change the metrics collector to take the data from the Metrics Store 2) Maybe aggregate the vms disk i/o on CFME side. This is not done in RHV, so not usre it makes sense. My initial thought was that aggregating the vms disk i/o data is actually the way it was supposed to work so I though it was a bug. Upon farther investigation it seems it is not a bug but actually an RFE (with different effort required depending on which of the options to choose) Please note that while the second option is much smaller to implement it has strange edge cases - what if you do a long vm migration? We need to decide how to resolve this, but currently the situation is that it depends on a DWH bug that was closed and there are no plans to fix it.
Moving to 5.10.3 to investigate CPU State and Network I/O issues mentioned in customer cases
Boris, Thank you for the detailed info, this BZ can be closed now.
The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have a bug that you are still able to reproduce on a current version of CloudForms please open a new bug.