What were you trying to do that didn't work?

When customers create their own sysctl drop-in executing after /etc/sysctl.d/99-sysctl.conf (which is a symlink to /etc/sysctl.conf, the setting gets overwritten by the ones set in /etc/sysctl.d/99-sysctl.conf when tuned service starts.

Through stracing tuned, we can see that /etc/sysctl.conf is applied after the drop-ins, whereas it should not.

Please provide the package NVR for which bug is seen:

tuned-2.22.1-1.el9.noarch

How reproducible:

Always

Steps to reproduce

1. Stop tuned

   # systemctl stop tuned

2. Add a sysctl in default file /etc/sysctl.conf

   echo "net.ipv4.ip_forward=0" >> /etc/sysctl.d/99-sysctl.conf

3. Create a drop-in alphanumerically ordered after 99-sysctl.conf, e.g. zzz-test.conf, overwriting the sysctl setting

   # echo "net.ipv4.ip_forward=1" > /etc/sysctl.d/zzz-test.conf

4. Apply the settings

   # systemctl restart systemd-sysctl
   # sysctl net.ipv4.ip_forward
   net.ipv4.ip_forward = 1
   

5. Start tuned

   # systemctl start tuned

Expected results

# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

Actual results

# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 0