Bug 1569018

Summary:	metrics from openshift 3.6 are not being collected properly by CloudForms 4.6.1
Product:	Red Hat CloudForms Management Engine	Reporter:	Felix Dewaleyne <fdewaley>
Component:	Providers	Assignee:	Bronagh Sorota <bsorota>
Status:	CLOSED DUPLICATE	QA Contact:	Dave Johnson <dajohnso>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.9.0	CC:	fdewaley, gblomqui, jfrey, jhardy, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-18 14:25:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Felix Dewaleyne 2018-04-18 13:58:02 UTC

Description of problem:
metrics from openshift 3.6 are not being collected properly by CloudForms 4.6.1 - the appliance thinks that there are no records while there definitely are and they are visible through hawkular 

Version-Release number of selected component (if applicable):
5.9.1 & ocp 3.6


How reproducible:
customer environment 

Steps to Reproduce:
1. connect ocp to 5.9.1 using the official guide [1]
2. enable metrics collection as documented and generate some load on ocp (only using hawkular, no prometeus in use)
3.

Actual results:]
[----] W, [2018-04-18T09:44:23.400910 #13357:d0910c]  WARN -- : MIQ(ManageIQ::Providers::Kubernetes::ContainerManager::MetricsCapture#perf_collect_metrics) Metrics missing: [ContainerGroup(20000000000098)] no gauge metrics found for [app-b-1-5nxbv]

Expected results:
metrics are collected for 3.6

Additional info:
[1] - https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/pdf/integration_with_openshift_container_platform/Red_Hat_CloudForms-4.6-Integration_with_OpenShift_Container_Platform-en-US.pdf

Comment 5 Felix Dewaleyne 2018-04-18 14:25:38 UTC


*** This bug has been marked as a duplicate of bug 1562090 ***