smartxworks
Failed to start Apply the …ngs specified in cloud-config.
Getting some errors during the "Waiting for control plane to be initialized..." phase:
kubectl logs vm-quickstart-cp-dc74x-qrvvf
[ 12.822875] cloud-init[1039]: Cloud-init v. 22.3.4-0ubuntu1~22.04.1 running 'modules:config' at Thu, 01 Jun 2023 02:40:30 +0000. Up 12.67 seconds. [ 12.900775] cloud-init[1039]: 2023-06-01 02:40:30,914 - util.py[WARNING]: Running module locale (<module 'cloudinit.config.cc_locale' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_locale.py'>) failed [ 12.939189] cloud-init[1039]: 2023-06-01 02:40:30,952 - cc_set_passwords.py[WARNING]: Ignoring config 'ssh_pwauth: None'. SSH service 'ssh' is not installed. [FAILED] Failed to start Apply the …ngs specified in cloud-config. See 'systemctl status cloud-config.service' for details. Starting Execute cloud user/final scripts...
[ 57.034344] cloud-init[1055]: CGROUPS_BLKIO: missing [ 57.035390] cloud-init[1055]: [WARNING SystemVerification]: missing optional cgroups: blkio [ 57.037697] cloud-init[1055]: [WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "", err: exec: "modprobe": executable file not found in $PATH
[ 101.474076] cloud-init[1055]: [kubelet-check] Initial timeout of 40s passed. [ 322.483336] cloud-init[1055]: Unfortunately, an error has occurred: [ 322.497123] cloud-init[1055]: timed out waiting for the condition [ 322.501165] cloud-init[1055]: This error is likely caused by: [ 322.501887] cloud-init[1055]: - The kubelet is not running [ 322.509514] cloud-init[1055]: - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
Please give me some advice how to solve this problem, TKS
@shengslin I'm glad to see you have solved the issue https://github.com/smartxworks/virtink/issues/93, and the reason was the K8S images cannot be pulled! Actually, we have packed the container images of K8S 1.24.0 into the control-plane/worker-machine-rootfs-image-1.24.0 and imported them before running kubeadm init command, so there is no need to pull these container images from the internet when initializing control-plane. I'm not sure why these container images were pulled from the internet in this issue, did you set the flag kubernetes-version to version other than 1.24.0 ?
