Created attachment 1650123 [details] must gather Description of problem: In IPv6 cluster metrics from kube-apiserver-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:
It should be `openshift-kube-apiserver-operator/kube-apiserver-operator/0` instead of `openshift-apiserver-operator/openshift-apiserver-operator/0`.
Verified with OCP build ipv6 4.4.0-0.nightly-2020-03-23-010639, metrics service of kube-apiserver is up. Go to prometheus UI -> menu(Status) -> Drop-down list(Targets), search keyword with “openshift-kube-apiserver-operator” in page, openshift-kube-apiserver-operator/kube-apiserver-operator/0 (1/1 up): https://[fd01::1:68f4:caff:fe00:24]:8443/metrics up endpoint="https" instance="[fd01::1:68f4:caff:fe00:24]:8443" job="metrics" namespace="openshift-kube-apiserver-operator" pod="kube-apiserver-operator-6ffffbdb75-nj6dv" service="metrics"
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. https://access.redhat.com/errata/RHBA-2020:0581