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.

Document URL: 

Section Number and Name: 

Describe the issue: 
~~~~
RHEL 7 onward /etc/sysctl.conf is added in initramfs by dracut.

This changes enable systems to apply network and other configuration immediately at boot, before the actual root partitions is mounted. This is important for some environments in particular, those with root on the network.

Also this improvement can cause some un-wanted problems.
This changes get populated to initramfs once its created by dracut.
Any mistake/temporary changes can make the systems apparently un-bootable.

One of our strategic customer requested to get this behavior documented in product documentation.
~~~~
Suggestions for improvement: 


Additional information:

Hello Maxim ,

>>Is it the same problem as in [1]? If so, is the solution [2] sufficient?

Yes both are same (even the related sfdc case is same) and the documentation looks perfect !

Thanks,
--Shatadru