Created attachment 1650130 [details] must gather Description of problem: In IPv6 cluster metrics from kube-scheduler-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-scheduler-operator/kube-scheduler-operator/0` is DOWN Expected results: `openshift-kube-scheduler-operator/kube-scheduler-operator/0` is UP Additional info:
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