Bug 1612776

Summary:	The ARP cache size did not been set in nodes except master node
Product:	OpenShift Container Platform	Reporter:	zhaozhanqi <zzhao>
Component:	Installer	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED ERRATA	QA Contact:	zhaozhanqi <zzhao>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.11.0	CC:	akamra, aos-bugs, gpei, hongli, jokerman, mmccomas, nelluri, wmeng
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-10 09:03:57 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:

Description zhaozhanqi 2018-08-06 09:00:36 UTC

Description of problem:
After setup OCP 3.11 cluster. found the ARP cache did not been set on node:
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
net.ipv6.neigh.default.gc_thresh1 = 128
net.ipv6.neigh.default.gc_thresh2 = 512
net.ipv6.neigh.default.gc_thresh3 = 1024

Version-Release number of the following components:
rpm -q openshift-ansible
openshift-ansible-roles-3.11.0-0.11.0.git.0.3c66516None.noarch.rpm

oc v3.11.0-0.11.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

How reproducible:

Steps to Reproduce:
1. Setup the 3.11 OCP cluster with openshift-ansible
2. Check the ARP cache size on nodes (except master node)
   sysctl -a | grep "neigh.default.gc_thresh"
3.

Actual results:
 sysctl -a | grep "neigh.default.gc_thresh"
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
net.ipv6.neigh.default.gc_thresh1 = 128
net.ipv6.neigh.default.gc_thresh2 = 512
net.ipv6.neigh.default.gc_thresh3 = 1024


Expected results:

net.ipv4.neigh.default.gc_thresh1 = 8192
net.ipv4.neigh.default.gc_thresh2 = 32768
net.ipv4.neigh.default.gc_thresh3 = 65536
net.ipv6.neigh.default.gc_thresh1 = 8192
net.ipv6.neigh.default.gc_thresh2 = 32768
net.ipv6.neigh.default.gc_thresh3 = 65536

Additional info:

when I restart 'tuned' service on the node. the values will become the correct one.

Comment 1 Scott Dodson 2018-08-16 13:57:04 UTC

This is probably a situation where node-config.yaml does not trigger the desired configuration to be applied by tuned because at the time tuned is started it doesn't have the labels expected. node-config.yaml is updated during the bootstrap process. We need to figure out a way to trigger tuned to be restarted.

Comment 2 Jiří Mencák 2018-08-16 14:05:04 UTC

We might be able to use what Seth suggests in BZ1569917, i.e. match against BOOTSTRAP_CONFIG_NAME in /etc/sysconfig/atomic-openshift-node until tuned is shipped containerized and uses its own logic to get node labels.  Will try to look into it and create a PR today/tomorrow.

Comment 4 Scott Dodson 2018-09-12 14:42:25 UTC

Because this isn't a regression between 3.10 and 3.11, aka it's broken in 3.10 too, I'm moving this to 3.11.z as it does not meet the criteria for 3.11.0 blocker.

Comment 7 Jiří Mencák 2018-11-09 18:05:23 UTC

Addressed upstream by https://github.com/openshift/openshift-ansible/pull/10102

Comment 8 zhaozhanqi 2018-11-12 03:04:13 UTC

Verified this bug on openshift-ansible-4.0.0-0.52.0.git.0.24249e7.el7.noarch.rpm

Comment 10 errata-xmlrpc 2019-01-10 09:03:57 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-2019:0024