-
Bug
-
Resolution: Done
-
Normal
-
4.15, 4.16
-
No
-
False
-
Description of problem:
Shared cpus are being removed from a container's cgroups, after Kubelet restart. This happens because after Kubelet restart the CPU manager reconciliation loop get triggered. It sends a container update request without the shared cpus (because CM manager is not aware of the shared cpus concept). We should add the shared cpus on CRI-O side again.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create pod that request for shared cpus 2. Check the pod cgroups - the shared cpus are in its cpuset 3. Restart Kubelet on the node where the pod stays. 4. Check the pod cgroups - the shared cpus are no longer in its cpuset while they should.
Actual results:
The shared cpus are no longer in the container's cgroup cpuset after Kubelet restart
Expected results:
The shared cpus should be under container's cgroup cpuset after Kubelet restart
Additional info:
- is blocked by
-
OCPBUGS-25926 crio: mixedcpus: shared cpus removed after kubelet restart
-
- Closed
-
- links to