-
Bug
-
Resolution: Done
-
Major
-
None
-
4.18
-
None
-
Important
-
None
-
Proposed
-
False
-
-
Description of problem:
Deleting a profile with annotation tuned.openshift.io/deferred: update, then apply the same profile again, the profile will immediately apply. Then edit the profile and change to a new value, reboot first time, the new value applied, then reboot again, it will restore to default value.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a new OCP using latest 4.18 nightly version 2. Creating a profile with annotation tuned.openshift.io/deferred: update 3. The profile will immediately apply. 4. Then edit the profile and change to a new value 5. reboot node twice, the sysctl value will restore to default value.
Actual results:
After rebooting node twice, the specified sysctl value will revert to default value
Expected results:
the specified sysctl value should keep the value as setting in tuned profile More detailed step, please check the second issue in the doc https://docs.google.com/document/d/1h-7AIyqf7sHa5Et2XF7a-RuuejwVkrjhiFFzqZnNfvg/edit
Additional info:
- duplicates
-
OCPBUGS-38795 Incorrect status message of profile when creating tuned profile prior to label nodes
- Verified