Description of problem: node-exporter cannot start due to incorrect IP address representation Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Tested with 4.4.0-0.nightly-2020-03-23-010639, issue is fixed $ oc -n openshift-monitoring get pod -o wide | grep node-exporter node-exporter-h4wlq 2/2 Running 2 15h fd2e:6f44:5dd8:c956::143 master-2.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-n8nd5 2/2 Running 2 15h fd2e:6f44:5dd8:c956::144 worker-3.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-s45vn 2/2 Running 2 15h fd2e:6f44:5dd8:c956::115 master-0.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-s4lx2 2/2 Running 2 15h fd2e:6f44:5dd8:c956::107 worker-0.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-vwq9j 2/2 Running 2 15h fd2e:6f44:5dd8:c956::142 worker-1.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-xh4rt 2/2 Running 2 15h fd2e:6f44:5dd8:c956::129 master-1.ocp-edge-cluster.qe.lab.redhat.com <none> <none> node-exporter-xtqm7 2/2 Running 2 15h fd2e:6f44:5dd8:c956::119 worker-2.ocp-edge-cluster.qe.lab.redhat.com <none> <none> $ oc -n openshift-monitoring get ds/node-exporter -oyaml | grep "secure-listen-address" - --secure-listen-address=[$(IP)]:9100 All node-exporter endpoints 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. https://access.redhat.com/errata/RHBA-2020:0581