-
Bug
-
Resolution: Done
-
Critical
-
4.13.0, 4.14.0
-
Critical
-
No
-
False
-
-
-
7/12: 4.13.z backport merged (https://github.com/cri-o/cri-o/pull/7013), should be good for 4.13.5 (dev cutoff Jul 12, fast channel Jul 18)
Description of problem:
Deployment of a standard masters+workers cluster using 4.13.0-rc.6 does not configure the cgroup structure according to OCPNODE-1539
Version-Release number of selected component (if applicable):
OCP 4.13.0-rc.6
How reproducible:
Always
Steps to Reproduce:
1. Deploy the cluster 2. Check for presence of /sys/fs/cgroup/cpuset/system* 3. Check the status of cpu balancing of the root cpuset cgroup (should be disabled)
Actual results:
No system cpuset exists and all services are still present in the root cgroup with cpu balancing enabled.
Expected results:
Additional info:
The code has a bug we missed. It is nested under the Workload partitioning check on line https://github.com/haircommander/cluster-node-tuning-operator/blob/123e26df30c66fd5c9836726bd3e4791dfd82309/pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go#L251
- blocks
-
OCPBUGS-10600 [OCP 4.13] Telco DPDK performance degradation
- Closed
-
OCPBUGS-13163 [4.13] cgroupv1 support for cpu balancing is broken for non-SNO nodes
- Closed
- clones
-
OCPBUGS-13148 cgroupv1 support for cpu balancing is broken for non-SNO nodes
- Closed
- is blocked by
-
OCPBUGS-13148 cgroupv1 support for cpu balancing is broken for non-SNO nodes
- Closed
- links to
(1 links to)