-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.14, 4.16, 4.18, 4.19
Description of problem:
Deploying RAN RDS configuration with non-RT kernel cause Cluster Compare to report it as a deviation!
Version-Release number of selected component (if applicable):
4.19
How reproducible:
100%
Steps to Reproduce:
1. Add non-RT kernel configuration to ztp-site-conifg
2. Deploy
Actual results:
Differences found in CR: tuned.openshift.io/v1_Tuned_openshift-cluster-node-tuning-operator_performance-patch, Compared To Reference CR: required/node-tuning-operator/TunedPerformancePatch.yaml
diff -u -N /tmp/MERGED-2769154737/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch /tmp/LIVE-4293073945/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch
--- /tmp/MERGED-2769154737/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch 2024-12-05 21:52:44.019791437 -0500
+++ /tmp/LIVE-4293073945/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch 2024-12-05 21:52:44.020791457 -0500
@@ -16,6 +16,10 @@
[service]
service.stalld=start,enable
service.chronyd=stop,disable
+ #### v Added for non-RT kernel v ###
+ [sysctl]
+ kernel.timer_migration=0
+ #### ^ Added for non-RT kernel ^ ###
name: performance-patch
recommend:
- machineConfigLabels:
Expected results:
Since it's a supported deployment configuration, this should not cause a deviation for cluster compare tool
Additional info:
It actually seems like the main toggle
realTimeKernel:
enabled: false
is not causing deviation, so probably it just needs to include the timer_migration into the exclusion?
- blocks
-
-
- Verified
-
- is cloned by
-
-
- Verified
-
- links to