e2e: fixed flaky test_id:32646 CPU load balancing on cgroupv1#1457
e2e: fixed flaky test_id:32646 CPU load balancing on cgroupv1#1457SargunNarula wants to merge 1 commit intoopenshift:mainfrom
Conversation
The test was flaky because it checked /proc/schedstat immediately after pod startup, before kubelet had time to reconcile system pod cpusets. This race window caused intermittent failures where load balancing appeared still enabled on the Guaranteed pod's CPUs. On cgroupv1 systems, disabling CPU load balancing requires ALL cgroups that intersect with a CPU to have sched_load_balance=0. Signed-off-by: Sargun Narula <snarula@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: SargunNarula The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@SargunNarula: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1 participant
The test was flaky because it checked /proc/schedstat immediately after pod startup, before kubelet had time to reconcile system pod cpusets. This race window caused intermittent failures where load balancing appeared still enabled on the Guaranteed pod's CPUs.
On cgroupv1 systems, disabling CPU load balancing requires ALL cgroups that intersect with a CPU to have sched_load_balance=0.