-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13.0, 4.14.0
-
None
-
Moderate
-
No
-
False
-
-
N/A
-
4/4/2023: PR created from a cherrypick
This is a clone of issue OCPBUGS-11083. The following is the description of the original issue:
—
Description of problem:
Updating performance profile test lane is flaky due to :
1. race conditions in tuned status checks:
After enabling realtime and high power consumption under workload hints in the performance profile, the test is falling since it cannot find stalld pid: msg: "failed to run command [pidof stalld]: output \"\"; error \"\"; command terminated with exit code 1",
2. mishandled test skips when hardware is not sufficient for a test
3. Unnecessary waits for mcp status changes
in performance profile
[BeforeEach] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:370
[It] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:432
[FAILED] Timed out after 2400.001s.
Failed to find condition status by MCP "worker-test"
Expected
<v1.ConditionStatus>: False
to equal
<v1.ConditionStatus>: True
In [BeforeEach] at: /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:429 @ 04/03/23 04:55:54.23
Version-Release number of selected component (if applicable):
Openshift 4.14, 4.13
How reproducible:
Often (Flaky test)
- clones
-
OCPBUGS-11083 NTO: e2e: TuneD parameters check test is flaky
- Closed
- is blocked by
-
OCPBUGS-11083 NTO: e2e: TuneD parameters check test is flaky
- Closed
- links to