Bug 1814642

Summary:	service-catalog-apiserver-operator & service-catalog-controller-manager-operator metrics cannot be scraped in IPv6 cluster
Product:	OpenShift Container Platform	Reporter:	Fan Jia <jfan>
Component:	Service Catalog	Assignee:	Jesus M. Rodriguez <jesusr>
Status:	CLOSED WONTFIX	QA Contact:	Fan Jia <jfan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	jiazha, marobrie
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1788155	Environment:
Last Closed:	2020-05-19 17:28:58 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:
Bug Depends On:	1822359
Bug Blocks:

Description Fan Jia 2020-03-18 12:26:15 UTC

must gather

Description of problem:
In IPv6 cluster metrics from service-catalog-apiserver-operator & service-catalog-controller-manager-operator cannot be scraped due to connection refused error

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-18-145749-ipv6.1

How reproducible:
Always

Steps to Reproduce:
1. Start a cluster
2. Go to prometheus UI -> targets (this needs to be done with port-forward, due to https://bugzilla.redhat.com/show_bug.cgi?id=1788135, cmd: "-n openshift-monitoring port-forward svc/prometheus-operated 9090")

Actual results:
`openshift-service-catalog-apiserver-operator/openshift-service-catalog-apiserver-operator/0` is DOWN
`openshift-service-catalog-controller-manager-operator/openshift-service-catalog-controller-manager-operator/0` is DOWN


Expected results:
`openshift-service-catalog-apiserver-operator/openshift-service-catalog-apiserver-operator/0` is UP
`openshift-service-catalog-controller-manager-operator/openshift-service-catalog-controller-manager-operator/0` is UP

Comment 2 Jesus M. Rodriguez 2020-05-15 03:33:09 UTC

Bug has been reviewed this sprint.

Comment 3 Jesus M. Rodriguez 2020-05-19 17:28:58 UTC

This does not seem to be a high enough severity to fix. If the reporter deems it to be high or urgent, please reopen and set the severity appropriately. Closing won't fix.