+++ This bug was initially created as a clone of Bug #1824473 +++
+++ This bug was initially created as a clone of Bug #1823941 +++
Description of problem:
When tuned CR is created containing an error, fixing the the mistake in the CR does not update the tuned profile on the host. The tuned pod has to be manually restarted for the changes to take effect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # oc lable node NODE1 tuned=test
2. Create tuned CR with error the value kernel.pid_max=1048575 is set 2x.
- data: |
summary=A custom OpenShift IPS host profile
kernel.sem="128 1048576 32 32768"
- label: tuned
3. fix the tuned CR or delete and replace with fixed removing the duplicate kernel.pid_max
# oc delete tuned ips
# oc create -f fixed-ips.yaml
Tuned profile to get updated
In order for this to take effect the tuned pod has to be restarted manually
--- Additional comment from Ryan Howe on 2020-04-14 20:11:35 UTC ---
Typo in my steps
# oc lable node NODE1 tuned=ips
THe issue is still present I just typed up the steps wrong.
--- Additional comment from on 2020-04-16 07:22:31 UTC ---
Upstream fix for 4.5: https://github.com/openshift/cluster-node-tuning-operator/pull/123
--- Additional comment from on 2020-04-16 09:51:28 UTC ---
Upstream PR for 4.4: https://github.com/openshift/cluster-node-tuning-operator/pull/125
Upstream PR for 4.3: https://github.com/openshift/openshift-tuned/pull/38
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.