Bug 1320472 - Utilization data does not show up in CFME
Summary: Utilization data does not show up in CFME
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Federico Simoncelli
QA Contact: Dave Johnson
URL:
Whiteboard: containers
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 10:03 UTC by Tony
Modified: 2016-04-04 11:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-24 15:58:38 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
ashlifst: needinfo+


Attachments (Terms of Use)
CFME error log (244.59 KB, image/png)
2016-03-23 10:03 UTC, Tony
no flags Details

Description Tony 2016-03-23 10:03:35 UTC
Created attachment 1139449 [details]
CFME error log

Description of the problem:

After the metrics are set up with the router configured, there is no utilization data available in CFME


Version-Release number of selected component (if applicable):
CFME 5.5.3.2


How reproducible:
Always

Steps to Reproduce:
1.Configure hawkular metrics and the route to CFME. Verify the pods are available and the services are running
2.In the CFME, go to Configuration ---> Configure, choose the server and then check the desired settings on the right, except for Database synchronization and RHN Mirror, then click on save
3. Click on Containers --> Pods ---> select pod ---> Monitor ---> Utilization
4.Observe the message "No utilization data available"

Actual results:
No utilization data (graphs) appears

Expected results:
Graphs should be visible in CFME

Additional info:

Comment 2 Greg Blomquist 2016-03-24 13:53:06 UTC
Federico, can you take a look at this one?

Comment 3 Federico Simoncelli 2016-03-24 13:57:17 UTC
It seems that the router is unreachable. What's the status of the pods?

# oc get pods --all-namespaces

Comment 4 Tony 2016-03-24 14:11:29 UTC
            
(In reply to Federico Simoncelli from comment #3)
> It seems that the router is unreachable. What's the status of the pods?
> 
> # oc get pods --all-namespaces

All pods are running

NAMESPACE         NAME                         READY     STATUS    RESTARTS   AGE
default           jenkins-1-v4ite              1/1       Running   0          24d
default           management-metrics-1-279n4   1/1       Running   0          1d
openshift-infra   hawkular-cassandra-1-qbus1   1/1       Running   0          1d
openshift-infra   hawkular-metrics-c0skt       1/1       Running   0          1d
openshift-infra   heapster-gn2m3

Comment 5 Federico Simoncelli 2016-03-24 15:58:38 UTC
After discussing this with Tony we discovered that the master was not properly configured (hence port 5000 was unreachable).


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