Bug 1321561 - Metrics does not work in CFME
Summary: Metrics does not work in CFME
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Federico Simoncelli
QA Contact: Einat Pacifici
URL:
Whiteboard: container:c&u
Depends On:
Blocks: 1285899 1288489 1288551 1292852 1293688
TreeView+ depends on / blocked
 
Reported: 2016-03-28 12:13 UTC by Einat Pacifici
Modified: 2023-09-14 03:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-11 22:22:13 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evm.log (2.22 MB, application/x-gzip)
2016-03-28 12:13 UTC, Einat Pacifici
no flags Details

Description Einat Pacifici 2016-03-28 12:13:53 UTC
Created attachment 1140844 [details]
evm.log

Description of problem:

When selecting Utilization for any Container elements (pods, container, nodes etc.), no utilization data is shown. Message box: "No utilization data available"

This bug has been opened as tracking bug for: 

  https://bugzilla.redhat.com/show_bug.cgi?id=1321349
  https://bugzilla.redhat.com/show_bug.cgi?id=1321346

How reproducible:
100%

Steps to Reproduce:
1. Setup provider with Metrics related pods 
2. in CFME select Utilization 


Actual results:
Message box: "No utilization data available"

Expected results:
Graphs with correct and relevant Utilization data should be seen. 

Additional info:

Comment 2 Federico Simoncelli 2016-03-30 15:58:36 UTC
The issue on this BZ seems to be:

[----] I, [2016-03-28T06:46:22.643408 #49443:bb7998]  INFO -- : MIQ(ManageIQ::Providers::Kubernetes::ContainerManager::ContainerNode#perf_capture) [realtime] Skipping processing for ManageIQ::Providers::Kubernetes::ContainerManager::ContainerNode name: [ha-master1.qa.lab.tlv.redhat.com], id: [4] as no metrics were captured.

Error: [<html>
  <body>
    <h1>503 Service Unavailable</h1>
    No server available to handle the request.
  </body>
</html>
]


Which essentially means that the metrics were not deployed with the correct HAWKULAR_METRICS_HOSTNAME.

Make sure to deploy metrics setting the correct HAWKULAR_METRICS_HOSTNAME (master hostname).

Ping me if you still have issues.

Comment 3 Federico Simoncelli 2016-04-11 22:22:13 UTC
It seems that Einat has successfully deployed metrics (and verified other bugs). I am closing this. Feel free to reopen if you think there's something to handle here.

Comment 4 Red Hat Bugzilla 2023-09-14 03:20:09 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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