Describe the bug
The sysctl module within os_hardening does not supply true to the permanent option to the sysctl calls - which means that on reboot many of the setting are lost until puppet updates them again.
Expected behavior
sysctl calls should ensure that the changes are permanent (ie stored within the sysctl.conf file).
Actual behavior
sysctl calls only impact on the running kernel (ie values are not stored within the sysctl.conf file).
Example code
Run the os_hardening module - it will change sysctl values - no entries will be made to sysctl.conf.
It turns out that the sysctl function in our puppet environment was being picked up from the wrong provider - apologies. All works as expected now that is removed.
Describe the bug The sysctl module within os_hardening does not supply true to the permanent option to the sysctl calls - which means that on reboot many of the setting are lost until puppet updates them again.
Expected behavior sysctl calls should ensure that the changes are permanent (ie stored within the sysctl.conf file).
Actual behavior sysctl calls only impact on the running kernel (ie values are not stored within the sysctl.conf file).
Example code Run the os_hardening module - it will change sysctl values - no entries will be made to sysctl.conf.
OS / Environment RHEL / Rocky 9
Puppet Version