-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.17.z, 4.16.z, 4.18.z, 4.19
-
None
This is a clone of issue OCPBUGS-46592. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-46036. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45971. The following is the description of the original issue:
—
Description of problem:
Running "Tuned profile shouldn't be degraded" test might result with a warning log dumped saying the profile degraded, when it is not. This occurs only on VM's.
Version-Release number of selected component (if applicable):
How reproducible:
Run the followig command: on a VM worker node!
Steps to Reproduce:
1. ginkgo run --focus="tuned profile shouldn't be degraded"
Actual results:
[0m[rfe_id:27368][performance] [38;5;243mTuned CRs generated from profile [0m[1mTuned profile shouldn't be degraded[0m [38;5;204m[tier-0][0m [38;5;243m/go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/1_performance/performance.go:120[0m Dec 9 17:44:52.342: [INFO]: daemonset "node-inspector-ns" "node-inspector" desired 6 scheduled 6 ready 6 Dec 9 17:44:52.382: [INFO]: found daemon pod node-inspector-p9c7k for node ci-op-j1grgvsb-29eee-k9lq2-worker-a-z28cm Dec 9 17:44:52.609: [WARNING]: Tuned profile is degraded. A warning raised as the node is based on a VM. Error message: TuneD daemon issued one or more error message(s) during profile application. TuneD stderr: [38;5;10m• [0.467 seconds][0m
Expected results:
No errors logged.
Additional info:
Test link: https://github.com/openshift/cluster-node-tuning-operator/blob/master/test/e2e/performanceprofile/functests/1_performance/performance.go#L120
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:0650
OpenShift Container Platform 4.16.z bug fix update