-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.18
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Error from log:
expected container pid CPUset to be: 0-7 but got: 0-3 Expected
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
[sig-node][apigroup:config.openshift.io] CPU Partitioning node validation should have correct cpuset and cpushare set in crio containers [Suite:openshift/conformance/parallel]
Significant regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 85.29%.
Sample (being evaluated) Release: 4.18
Start Time: 2025-11-10T00:00:00Z
End Time: 2025-11-17T12:00:00Z
Success Rate: 85.29%
Successes: 29
Failures: 5
Flakes: 0
Base (historical) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-10-01T23:59:59Z
Success Rate: 100.00%
Successes: 1028
Failures: 0
Flakes: 1
View the test details report for additional context.
Filed by: cmeadors@redhat.com