Skip to content

Chicken and egg problem changing cgroup driver #1501

@NeilW

Description

@NeilW

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

kubeadm version (use kubeadm version):

kubeadm version: &version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:08:49Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Environment:

  • Kubernetes version (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:26:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

  • Cloud provider or hardware configuration:
    Brightbox

  • OS (e.g. from /etc/os-release):
    Ubuntu 18.04

  • Kernel (e.g. uname -a):
    Linux srv-fwu87 4.15.0-47-generic discuss CA checksum flag for kubeadm join #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  • Others:

What happened?

There doesn't appear to be a way of getting a kubeadm installation installed on the 'cgroupfs' Cgroup across to the 'systemd' cgroup when you receive the preflight error #1394

If you alter the docker config in 'daemon.json' to enable the systemd cgroup, then kubelet crashes with the error

kubelet[7257]: F0411 14:31:02.244445    7257 server.go:261] failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "cgroupfs" is different from docker cgroup driver: "systemd"

and kubeadm upgrade won't run

[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/health] FATAL: [preflight] Some fatal errors occurred:
	[ERROR ControlPlaneNodesReady]: there are NotReady control-planes in the cluster: [srv-fwu87]

What you expected to happen?

There should be a way to move from cgroupfs to systemd gracefully, or at least in a documented manner.

How to reproduce it (as minimally and precisely as possible)?

  • Install 1.13.5 cluster using standard docker.io package.
  • Add the daemon.json to set the cgroup, as shown here: https://kubernetes.io/docs/setup/cri/
  • restart docker.
  • Try to run a kubeadm upgrade to 1.14.1

Anything else we need to know?

Metadata

Metadata

Assignees

Labels

area/ecosystemkind/documentationCategorizes issue or PR as related to documentation.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions