Created attachment 1650128 [details] must gather Description of problem: In IPv6 cluster metrics from kube-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-kube-controller-manager-operator/kube-controller-manager-operator/0` is DOWN Expected results: `openshift-kube-controller-manager-operator/kube-controller-manager-operator/0` is UP Additional info:
*** Bug 1790430 has been marked as a duplicate of this bug. ***
Confirmed with payload 4.4.0-0.nightly-2020-03-23-010639, the issue has fixed: 1) one terminal use command: `oc -n openshift-monitoring port-forward svc/prometheus-operated 9090` 2) Second terminal check: [root@dhcp-140-138 ~]# curl -s http://localhost:9090/api/v1/targets | jq | grep "openshift-kube-controller-manager-operator/kube-controller-manager-operator/0" -C20 | grep "health" "health": "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. https://access.redhat.com/errata/RHBA-2020:0581