-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
-
None
-
3
-
False
-
Description of problem:
Duplicate TuneD profiles with the same name and different content cause periodic TuneD restarts
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
Create two custom Tuned CRs. Profile 1 apiVersion: tuned.openshift.io/v1 kind: Tuned metadata: name: openshift-profile-dup namespace: openshift-cluster-node-tuning-operator spec: profile: - data: | [main] summary=Custom OpenShift profile include=openshift-node [sysctl] kernel.shmmni=8192 name: openshift-profile recommend: - match: - label: profile priority: 20 profile: openshift-profile Profile 2 apiVersion: tuned.openshift.io/v1 kind: Tuned metadata: name: openshift-profile-dup2 namespace: openshift-cluster-node-tuning-operator spec: profile: - data: | [main] summary=Custom OpenShift profile include=openshift-node [sysctl] kernel.shmmni=8191 name: openshift-profile recommend: - match: - label: profile priority: 20 profile: openshift-profile
Actual results:
TuneD periodically restarting in 600s intervals.
Expected results:
User sufficiently informed about the misconfiguration (duplicate TuneD profiles) not only in the operator logs and TuneD not periodically restarting.
Additional info:
This has bitten us a few times in the past, most recently in https://access.redhat.com/support/cases/#/case/03940882 There is an associated TuneD issue with this, but it should not be a problem in NTO 4.14+ https://issues.redhat.com/browse/RHEL-60898