Bug 1795043 - Sysctl and upgrade kernel
Summary: Sysctl and upgrade kernel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-26 16:46 UTC by olegon.ru
Modified: 2021-11-30 17:46 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:46:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description olegon.ru 2020-01-26 16:46:54 UTC
1. Setup vm.overcommit_memory=2 & vm.overcommit_ratio=100 in /etc/sysctl.conf
2. sysctl -p
3. Upgrade the kernel (dnf --refresh upgrade)
4. Clean /etc/sysctl.conf by removing lines, added in step 1
5. Reboot

expected default values, i.e. vm.overcommit_memory=0 & vm.overcommit_ratio=50, because sysctl.conf is clean, BUT, now default values is current values of kernel upgrade time, vm.overcommit_memory=2 & vm.overcommit_ratio=100

Very confusing... It's impossible to return distribution kernel default values now.

Confirmed on three my Fedora machines (Fedora Gnome, Fedora Server and Fedora KDE spin), very surprised to found kernel parameter values, I setted up two years ago.

Comment 1 Justin M. Forbes 2020-03-03 16:29:59 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.

Comment 2 olegon.ru 2020-03-10 04:32:09 UTC
Confirmed at 5.5.8-200.fc31.x86_64

Comment 3 Ben Cotton 2020-11-03 16:14:56 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 olegon.ru 2021-01-21 19:56:48 UTC
It's misunderstanding and strange feature of dracut.
While kernel upgrade process run dracut -f, copy of /etc/sysctl.conf placed to initramfs.
So, if I wrote any parameter to /etc/sysctl.conf and upgrade kernel, all parameters in current /etc/sysctl.conf will be my default parameters, until I run dracut -f again.

Comment 5 Ben Cotton 2021-11-04 16:15:36 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-30 17:46:13 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.