Unknown "condition" error

[IK-Adrian]

What happened:
Unable to launch CloudCore with keadm.

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

sudo keadm init --advertise-address=A.B.C.D --profile version=v1.14.1

Raises the following error after a certain timeout:

Error: timed out waiting for the condition

There is no further information on what this condition is.

If we add the --force flag, the deployment is applied, but the pod crashes with the following error:

Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: open /sys/fs/cgroup/memory/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podXYZ.slice/cri-containerd-cloudcore.scope/memory.memsw.limit_in_bytes: no such file or directory: unknown

Environment:

• Kubernetes version (use kubectl version): 1.23.16

• KubeEdge version(e.g. cloudcore --version and edgecore --version): 1.14.1

• Cloud nodes Environment:

  • Hardware configuration: x86_64
  • OS: Ubuntu 20.04.3
  • Kernel: Linux ... 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[Shelley-BaoYue]

The error itself looks to be coming from containerd or runc. containerd/containerd#7828 may help you.