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: following a RHEL 7.6 to 7.7 upgrade, some network kernel parameters like net.ipv4.neigh.default.gc_thresh and net.netfilter.nf_conntrack_max are not being applied according to profile values. 

Post upgrade values:

# 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

Before upgrade:

# 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

Version-Release number of selected component (if applicable):
Before (RHEL 7.6): tuned - 2.10.0-6.el7_6.3
After (RHEL 7.7):  tuned - 2.11.0-5.el7fdp

Actual results: while the `tuned` profile is active, 

Expected results: tuned profile settings to be applied as before the RHEL 7.7 upgrade.

Additional info:
- sosreports extracted from before and after node upgrade
- The applied tuned profile is [1], which also includes [2].

---

[1] https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/tuned/templates/openshift/tuned.conf
[2] https://github.com/openshift/openshift-ansible/tree/release-3.11/roles/tuned/templates/openshift

*** This bug has been marked as a duplicate of bug 1749411 ***