You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the OS boots and the kubelet starts, it adds cpuset to /sys/fs/cgroup/cgroup.subtree_control. However, it seems that kubelet calls the runc method setUnitProperties, which in turn calls SetUnitPropertiesContext from the go-systemd library. At this point, we notice that the cpuset, which was already present, gets removed (for reasons unknown). This causes kubelet to restart, but this time, the cpuset gets added back and remains in /sys/fs/cgroup/cgroup.subtree_control.
After the OS boots and the kubelet starts, it adds
cpuset
to/sys/fs/cgroup/cgroup.subtree_control
. However, it seems that kubelet calls the runc method setUnitProperties, which in turn calls SetUnitPropertiesContext from the go-systemd library. At this point, we notice that thecpuset
, which was already present, gets removed (for reasons unknown). This causes kubelet to restart, but this time, thecpuset
gets added back and remains in/sys/fs/cgroup/cgroup.subtree_control
.More details are in the description of kubernetes/kubernetes#122955
On my local OCP node, I was able to observe this issue as well,
The text was updated successfully, but these errors were encountered: