Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1789000

Summary:	node-exporter not working in IPv6 environment
Product:	OpenShift Container Platform	Reporter:	Pawel Krupa <pkrupa>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.z	CC:	alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1789001 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:23:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1789001

Description Pawel Krupa 2020-01-08 14:44:16 UTC

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:

Comment 2 Junqi Zhao 2020-03-24 05:51:05 UTC

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

Comment 4 errata-xmlrpc 2020-05-04 11:23:07 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.

https://access.redhat.com/errata/RHBA-2020:0581