Bug 1788155 - service-catalog-apiserver-operator & service-catalog-controller-manager-operator metrics cannot be scraped in IPv6 cluster
Summary: service-catalog-apiserver-operator & service-catalog-controller-manager-opera...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.4.0
Assignee: Jesus M. Rodriguez
QA Contact: Fan Jia
Depends On: 1805456 1809238 1816121
TreeView+ depends on / blocked
Reported: 2020-01-06 14:52 UTC by Pawel Krupa
Modified: 2020-05-04 11:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1814642 (view as bug list)
Last Closed: 2020-05-04 11:22:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
must gather (18.92 MB, application/gzip)
2020-01-06 14:52 UTC, Pawel Krupa
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift cluster-svcat-apiserver-operator pull 77 0 None closed Bug 1788155: get ipv6 support from library-go bump; switch to go modules 2020-11-12 12:02:49 UTC
Github openshift cluster-svcat-controller-manager-operator pull 70 0 None closed Bug 1788155: get ipv6 support from library-go bump 2020-11-12 12:02:50 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:23:09 UTC

Description Pawel Krupa 2020-01-06 14:52:29 UTC
Created attachment 1650132 [details]
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):

How reproducible:

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 1 Jesus M. Rodriguez 2020-02-26 23:39:42 UTC
Bumped library-go to pull in the fix for Bug 1788521.
PR: openshift/library-go#657

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.

Comment 7 Fan Jia 2020-03-24 07:42:12 UTC
ipv6 cluster

test result:
The targets of openshift-service-catalog-apiserver-operator and openshift-service-catalog-controller-manager-operator in Prometheus UI are "up".

Comment 9 errata-xmlrpc 2020-05-04 11:22:33 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.


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