Bug 1788143

Summary: openshift-controller-manager-operator metrics cannot be scraped in IPv6 cluster
Product: OpenShift Container Platform Reporter: Pawel Krupa <pkrupa>
Component: openshift-controller-managerAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED DUPLICATE QA Contact: wewang <wewang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, mfojtik, scuppett
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-30 22:07:07 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 Pawel Krupa 2020-01-06 14:31:14 UTC 
Description of problem:
In IPv6 cluster metrics from openshift-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-apiserver-operator/openshift-apiserver-operator/0` is DOWN


Expected results:
`openshift-apiserver-operator/openshift-apiserver-operator/0` is UP


Additional info:
Comment 2 Pawel Krupa 2020-01-06 14:36:13 UTC 
It should be `openshift-controller-manager-operator/openshift-controller-manager-operator/0` instead of `openshift-controller-manager-operator/openshift-controller-manager-operator/0 `.
Comment 3 Stephen Cuppett 2020-01-06 16:07:36 UTC 
Moving to 4.4.0 for investigation, we'll need a 4.3.z Target Release clone created.
Comment 4 Adam Kaplan 2020-01-30 22:07:07 UTC 

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