Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Previously opened in BZ-1743619 due to the way this issue manifests itself in OpenShift environments.
net.ipv4.neigh.default.gc_thresh is not getting set even though this is set with the tuned profile.
Also net.netfilter.nf_conntrack_max is not getting set from the tuned openshift profile.
Version-Release number of selected component (if applicable):
tuned 2.11.0-5.el7_7.1
How reproducible:
Update OS from RHEL 7.6 to 7.7
Actual results:
# grep ipv4.neigh.*thresh sos_commands/kernel/sysctl_-a
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
# grep net.nf_conntrack_max sos_commands/kernel/sysctl_-a
net.nf_conntrack_max = 262144
Expected results:
This should be set instead:
net.ipv4.neigh.default.gc_thresh1=8192
net.ipv4.neigh.default.gc_thresh2=32768
net.ipv4.neigh.default.gc_thresh3=65536
Additional info:
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1743619 for prior troubleshooting efforts. This issue seems to affect any OpenShift 3.11 customers who update to RHEL7.7 from 7.6.
Comment 2Candace Sheremeta
2019-09-05 17:17:35 UTC
*** Bug 1749421 has been marked as a duplicate of this bug. ***
** Correction the before upgrade the systctls are set based on the tuned profile.
Before upgrade:
# sysctl net.ipv4.neigh.default.gc_thresh{1,2,3} net.netfilter.nf_conntrack_max
net.ipv4.neigh.default.gc_thresh1=8192
net.ipv4.neigh.default.gc_thresh2=32768
net.ipv4.neigh.default.gc_thresh3=65536
net.netfilter.nf_conntrack_max=1048576
Post upgrade values:
# sysctl net.ipv4.neigh.default.gc_thresh{1,2,3} net.netfilter.nf_conntrack_max
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
net.netfilter.nf_conntrack_max = 262144
After they get reverted to the defaults, restarting tuned does not set them back.
The sysctls can manually get set with out issue.
Next Steps: Can you get debug logs from tuned?
# systemctl stop tuned
- Set values back to default
- restart tuned to make sure the issue is present still
- Stop tuned
# systemctl stop tuned
- Get debug logs output running tuned yourself:
# tuned -D