Bug 1603144

Summary:	Installing prometheus should update iptable rules for node-exporter
Product:	OpenShift Container Platform	Reporter:	Simon Pasquier <spasquie>
Component:	Monitoring	Assignee:	Simon Pasquier <spasquie>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, bbilgin, dapark, gnunn, jokerman, juzhao, mmccomas, oourfali, pep, spasquie
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: the 9100 port is blocked on all nodes by default. Consequence: Prometheus can't scrape the node_exporter service running on the other nodes and which listens on port 9100. Fix: the firewall configuration is modified to allow incoming TCP traffic for the 9000-1000 port range. Result: Prometheus can scrape the node_exporter services.	Story Points:	---
Clone Of:	1563888	Environment:
Last Closed:	2018-08-29 14:42:32 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:	1563888
Bug Blocks:	1600562

Comment 2 Junqi Zhao 2018-08-22 05:33:51 UTC

node-exporter 9100 port is open on nodes which node-exporter pods are running at, for example:
# netstat -anlp | grep 9100
tcp6       0      0 :::9100                 :::*                    LISTEN      54236/node_exporter 
tcp6       0      0 172.16.120.88:9100      10.128.0.10:56394       ESTABLISHED 54236/node_exporter 

and node-exporter target could be accessed without error

env:
openshift-ansible-3.9.41-1.git.0.4c55974.el7.noarch
prometheus-node-exporter:v3.9.41

# openshift version
openshift v3.9.41
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

Comment 4 errata-xmlrpc 2018-08-29 14:42:32 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-2018:2549