Bug 1415067

Summary:	[3.2]Installer should persist net.ipv4.ip_forward
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Installer	Assignee:	Tim Bielawa <tbielawa>
Status:	CLOSED ERRATA	QA Contact:	Wenkai Shi <weshi>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	abhgupta, aos-bugs, bbennett, gpei, jialiu, jkaur, jokerman, mmccomas, sdodson, tbielawa
Target Milestone:	---
Target Release:	3.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Network Manager resets the net.ipv4.ip_forward parameter Consequence: OpenShift loses certain functionality. Fix: The installer sets the sysctl parameter on the system level now. Result: Network manager restarts no longer interfere with the installation process.	Story Points:	---
Clone Of:	1372388	Environment:
Last Closed:	2017-03-06 16:37:45 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:	1372388, 1477716
Bug Blocks:	1415046

Comment 2 Scott Dodson 2017-01-20 16:06:51 UTC

Workaround is to run the following

echo "net.ipv4.ip_forward=1" >> /etc/sysctl.conf
sysctl -w net.ipv4.ip_forward=1

Comment 3 Tim Bielawa 2017-02-01 19:24:45 UTC

Backport submitted in this PR:

https://github.com/openshift/openshift-ansible/pull/3247

Comment 5 Wenkai Shi 2017-02-07 05:26:43 UTC

Verified with version atomic-openshift-utils-3.2.47-1.git.0.34a924d, the "net.ipv4.ip_forward" setting is persisted on nodes.

[root@node ~]# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

[root@node ~]# grep net.ipv4.ip_forward /etc/sysctl.conf
net.ipv4.ip_forward=1

Comment 7 errata-xmlrpc 2017-03-06 16:37:45 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/RHSA-2017:0448