Bug 1301861 - Metrics does not show information for pods/containers
Summary: Metrics does not show information for pods/containers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Yaacov Zamir
QA Contact: Shalom Naim
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-26 08:22 UTC by Einat Pacifici
Modified: 2018-08-28 09:54 UTC (History)
9 users (show)

Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 15:33:27 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
snaim: automate_bug+


Attachments (Terms of Use)
evm.log attached. (4.33 MB, application/x-gzip)
2016-01-26 08:22 UTC, Einat Pacifici
no flags Details
screenshot.png (104.73 KB, image/png)
2016-01-26 08:56 UTC, Federico Simoncelli
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Einat Pacifici 2016-01-26 08:22:45 UTC
Created attachment 1118385 [details]
evm.log attached.

Description of problem:
Metrics does not show information for pods/containers when selecting Utilization information. 

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

How reproducible:
Always

Steps to Reproduce:
1.Setup CFME to enable Metrics 
2.Select a Pod in CFME : Containers --> Pods
3.Select Monitoring --> Utilization

Actual results:
Error is shown: No Utilization Data Available


Expected results:
Utilization data + graphs should be seen. 


Additional info:
EVM log attached.

Comment 2 Federico Simoncelli 2016-01-26 08:36:56 UTC
The error seems related to the fact that there are no information on the nodes cores. Please go into the nodes summary page and check that they all have capacity information (cpu and memory).

Sadly this information is not available in the logs.

Feel free to ping me on IRC and we'll look at it together.

Comment 3 Federico Simoncelli 2016-01-26 08:56:54 UTC
Created attachment 1118393 [details]
screenshot.png

Looking in Einat's environment I found one node that was defined but never reported any information (see screenshot).

Since we have fixed bug 1288549 we are now able to deal with nodes that never reported any information but now they're breaking metrics collection.

Comment 4 Federico Simoncelli 2016-01-26 09:08:54 UTC
Best way to address this is to catch the validation error and return empty metrics for the relevant object.

Comment 5 Federico Simoncelli 2016-04-22 14:57:22 UTC
I think that this is easy to reproduce. It's just a matter to add a new dummy node in OpenShift (that doesn't exists) and see what breaks in ManageIQ (inventory refresh and metrics collection).

Yaacov can you give it a try? Thanks.

Comment 6 Yaacov Zamir 2016-04-27 12:38:24 UTC
Submited upstream:
https://github.com/ManageIQ/manageiq/pull/8213

Comment 7 Federico Simoncelli 2016-05-12 21:41:39 UTC
Yaacov shouldn't this be moved to POST?

Comment 9 errata-xmlrpc 2016-06-29 15:33:27 UTC
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, 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/RHBA-2016:1348


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