-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
None
-
Important
-
None
-
Proposed
-
False
-
-
Release Note Not Required
-
In Progress
-
Description of problem:
Creating a tuned profile with annotation tuned.openshift.io/deferred: "update" first before label target node, then label node with profile=, the value of kernel.shmmni applied immediately. but it shows the message [The TuneD daemon profile is waiting for the next node restart: openshift-profile], then reboot nodes, it will restore to default value of kernel.shmmni, not setting to expected value.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Creating OCP cluster with latest 4.18 nightly version 2. Create tuned profile before label node please refer to issue 1 if you want to reproduce the issue in the doc https://docs.google.com/document/d/1h-7AIyqf7sHa5Et2XF7a-RuuejwVkrjhiFFzqZnNfvg/edit
Actual results:
It should show the message [TuneD profile applied]. the sysctl value should keep as expect after node reboot
Expected results:
It shouldn't show the message The TuneD daemon profile is waiting for the next node restart: openshift-profile when executing oc get profile also the sysctl value shouldn't revert after node reboot
Additional info:
- is duplicated by
-
OCPBUGS-38796 The sysctl value will revert after reboot node twice when create profile with tuned.openshift.io/deferred: "update" annotation
- Closed
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update