Check for /sys/fs/cgroup/cpu/cpu.cfs_quota_us / config_cfs_bandwith on init #2335
Description
What keywords did you search in kubeadm issues before filing this one?
cfs_quota_us aarch64 centos8 cri-o crio
Oct 24 01:00:44 chaos kubelet[14438]: E1024 01:00:44.465714 14438 kuberuntime_manager.go:804] container &Container{Name:etcd,Image:k8s.gcr.io/etcd:3.4.13-0,Command:[etcd --advertise-client-urls=https://192.168.1.70:2379 --cert-file=/et>
Oct 24 01:00:44 chaos kubelet[14438]: time="2020-10-24T01:00:44Z" level=error msg="container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \\\"process_linux.go:415: setting cgroup config fo>
Oct 24 01:00:44 chaos kubelet[14438]: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:415: setting cgroup config for procHooks process caused \\\"failed to write \>
Oct 24 01:00:44 chaos kubelet[14438]: E1024 01:00:44.465863 14438 pod_workers.go:191] Error syncing pod e0f6df37808b0e77cc354267a4dc6b38 ("etcd-chaos_kube-system(e0f6df37808b0e77cc354267a4dc6b38)"), skipping: failed to "StartContainer">
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
As seen in:
cri-o/cri-o#4307
https://bugs.centos.org/view.php?id=17813
kubeadm should check for the existance of /sys/fs/cgroup/cpu/cpu.cfs_quota_us. It missing is a sign of the kernel being compiled without config_cfs_bandwith which results in the errors above and a failed kubeadm init.
Versions
kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:47:53Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/arm64"}