Bug 2064755

Summary:	nf_conntrack_hashsize in [net] doesn't work when kernel module nf_conntrack isn't loaded
Product:	Red Hat Enterprise Linux 9	Reporter:	Robin Hack <rhack>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED WONTFIX	QA Contact:	Robin Hack <rhack>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jeder, jskarvad
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-16 07:28: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:

Description Robin Hack 2022-03-16 13:49:05 UTC

Description of problem:
Create profile with:
[net]
nf_conntrack_hashsize=131072

enable profile

Take a look at logs:
2022-03-16 09:41:56,931 ERROR    tuned.utils.commands: Error when reading file '/sys/module/nf_conntra
ck/parameters/hashsize': '[Errno 2] No such file or directory: '/sys/module/nf_conntrack/parameters/hashsize''
2022-03-16 09:41:56,931 ERROR    tuned.utils.commands: Writing to file '/sys/module/nf_conntrack/parameters/hashsize' error: '[Errno 2] No such file or directory: '/sys/module/nf_conntrack/parameters/hashsize''


After: 
# modprobe nf_conntrack
there is no issue in logs

Version-Release number of selected component (if applicable):
tuned-2.18.0-1.el9.noarch

How reproducible:
always


Actual results:
Kabooom

Expected results:
No kabooom

Comment 1 Jaroslav Škarvada 2022-05-23 13:24:32 UTC

We have currently +r flag to force reload:
[modules]
MODULE=+r OPTION=VALUE

We could add e.g. the 'f' or 'c' flag to handle this situation, e.g.:
[modules]
MODULE1=+rf OPTION=VALUE
MODULE2=+fr OPTION=VALUE
MODULE3=+f OPTION=VALUE

Comment 5 RHEL Program Management 2023-09-16 07:28:45 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.