-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Description of problem:
Around 25th of Feb jobs for 4.17 and 4.18 started failing. The fails are about single core exceeding latency threshold. Investigation showed that oslat Pod started getting assigned CPUs that are not isolated and should be offline. More investigation showed that the problem probably lies in the tuned package in the EUS repository (for some reason successful 4.19 got even newer package from fast-datapath).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
Successful 4.19: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-footprint-and-performance-nightly/1897089856383750144 Last successful 4.18: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-footprint-and-performance-nightly/1893828511341219840 Failing 4.18: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-footprint-and-performance-nightly/1897089851338002432 Failing 4.17: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.17-footprint-and-performance-nightly/1897089847164669952
- is caused by
-
-
- Closed
-
- links to