Bug 1467756 - CloudForms does not show region-level Utilization from "Optimize" -> "Utilization" menu [NEEDINFO]
CloudForms does not show region-level Utilization from "Optimize" -> "Utiliza...
Status: ON_DEV
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting (Show other bugs)
Unspecified Unspecified
medium Severity high
: GA
: cfme-future
Assigned To: Gregg Tanzillo
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2017-07-04 21:45 EDT by tachoi
Modified: 2017-09-12 13:44 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
tachoi: needinfo? (gtanzill)
tachoi: needinfo? (gtanzill)
tachoi: needinfo? (gtanzill)
tachoi: needinfo? (gtanzill)

Attachments (Terms of Use)

  None (edit)
Description tachoi 2017-07-04 21:45:14 EDT
Description of problem:
Login to CloudForms and select "Optimize" -> "Utilization", and then the "Details" report, all of the chart data points are either "0Mhz" (trend of CPU used), "0B" (trend of RAM used) or "0B" (trend of used disk space).

Having C&U collection for the region set to "Collect for all clusters" and "Collect for all datastores". In addition, already verified that all instances are reporting CPU, RAM and Disk IO metrics via OSP Gnocchi, and this is visible in the CFME UI.

Version-Release number of selected component (if applicable):
OSP 10 with Gnocchi configured for metrics collection

How reproducible:
See below

Steps to Reproduce:
1. Add OSP 10 provider to CFME 
2. Setup metrics collection from CFME as well as OSP10 side
3. Check metrics info is available from instance level
4. Navigate to "Optimize" -> "Utilization" UI for region level report.

Actual results:
No data available 

Expected results:
Corresponding date is reported

Additional info:
Had a check with CFME 4.8.0, having same issue.

Note You need to log in before you can comment on or make changes to this bug.