Bug 1789001

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:	low	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	alegrand, anpicker, erooth, juzhao, kakkoyun, lcosic, mloibl, pkrupa, surbania, xtian
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1789000	Environment:
Last Closed:	2020-01-23 11:20:00 UTC	Type:	---
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:	1789000
Bug Blocks:

Description Pawel Krupa 2020-01-08 14:47:02 UTC

+++ This bug was initially created as a clone of Bug #1789000 +++

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. Start a cluster
2.
3.

Actual results:
node-exporter is Crashlooping


Expected results:
node-exporter works

Additional info:

Comment 6 errata-xmlrpc 2020-01-23 11:20:00 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:0062