Skip to content

[sig-node][CPU Manager][Failing test] When running non-guaranteed pods tests should let the container access all the online CPUs without a reserved CPUs set #131769

@esotsal

Description

@esotsal

Failure cluster 6f1ebcdff366821299a0

https://storage.googleapis.com/k8s-triage/index.html?text=%20k8s.io%2Fkubernetes%2Ftest%2Fe2e_node%2Fcpumanager_test.go%3A193

Error text:
[FAILED] open /sys/fs/cgroup/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podd0214f4c_870d_45ee_b40d_80c9db363992.slice/cri-containerd-c7313a54b4850605025748a1cdafb98d9a0e2b4e3daa32780c3925d913e94b68.scope/cpuset.cpus.effective: no such file or directory
In [It] at: k8s.io/kubernetes/test/e2e_node/cpumanager_test.go:193 @ 05/10/25 04:34:45.956

Recent failures:

5/14/2025, 11:16:36 AM ci-cgroupv1-containerd-node-arm64-e2e-serial-ec2-eks
5/14/2025, 10:21:35 AM ci-cgroupv1-containerd-node-e2e-serial-ec2-eks
5/14/2025, 5:17:08 AM ci-cgroupv1-containerd-node-arm64-e2e-serial-ec2-eks
5/14/2025, 4:21:32 AM ci-cgroupv1-containerd-node-e2e-serial-ec2-eks
5/13/2025, 11:16:34 PM ci-cgroupv1-containerd-node-arm64-e2e-serial-ec2-eks

Image

/kind failing-test

/sig node

Metadata

Metadata

Assignees

Labels

kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

Triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions