(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]

This is on RHCOS10

Error was:
fail [github.com/openshift/origin/test/extended/cpu_partitioning/crio.go:216]: node: ci-op-5rx0id2d-58b87-8zkcb-worker-a-5v889 pod: openshift-machine-config-operator/kube-rbac-proxy-crio-ci-op-5rx0id2d-58b87-8zkcb-worker-a-5v889 container: kube-rbac-proxy-crio | expected container pid CPUset to be: 0-7 but got: 0-3

Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 0.00%.

Sample (being evaluated) Release: 4.22
Start Time: 2026-01-23T00:00:00Z
End Time: 2026-01-30T12:00:00Z
Success Rate: 0.00%
Successes: 0
Failures: 12
Flakes: 0
Base (historical) Release: 4.22
Start Time: 2025-12-31T00:00:00Z
End Time: 2026-01-30T12:00:00Z
Success Rate: 100.00%
Successes: 110
Failures: 0
Flakes: 1

View the test details report for additional context.

Filed by: cmeadors@redhat.com