Created attachment 1650132 [details]
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):
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")
`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
`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
Bumped library-go to pull in the fix for Bug 1788521.
The default bind network was tcp4, library-go switch it to tcp
which will support ipv6.
The bug states the following:
We use SetRecommendedServingInfoDefaults() in library-go across
all operators to provide defaults for API servers that those
operators run to serve metrics and healthz
Also pinned openshift/api & openshift/client-go to match the release.
The targets of openshift-service-catalog-apiserver-operator and openshift-service-catalog-controller-manager-operator in Prometheus UI are "up".
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.