kubesphere: All-in-one installer not working.
Describe the bug(描述下问题) A clear and concise description of what the bug is.
all-in-one installer not working.
Versions used(KubeSphere/Kubernetes的版本) KubeSphere: Advanced 2.0.2
Environment(环境的硬件配置) How many nodes and their hardware configuration: All in one installer. 8cpu / 16gb ram / 200gb disk / Ubuntu 18.04.3 LTS latest updated as of today.
To Reproduce(复现步骤) Steps to reproduce the behavior:
- Boot fresh VM using ubuntu 18.04 LTS
- Install latest updates.
- Follow all in one installer docs.
./install.sh
Last few lines from installer script:
TASK [kubernetes/master : kubeadm | Initialize first master] ***********************************************************************************************************************************
Sunday 03 November 2019 08:09:33 -0800 (0:00:00.117) 0:02:42.129 *******
fatal: [ks-allinone]: FAILED! => {"changed": true, "cmd": ["timeout", "-k", "600s", "600s", "/usr/local/bin/kubeadm", "init", "--config=/etc/kubernetes/kubeadm-config.yaml", "--ignore-preflight-errors=all"], "delta": "0:05:05.880681", "end": "2019-11-03 08:14:39.493151", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2019-11-03 08:09:33.612470", "stderr": "\t[WARNING FileExisting-ethtool]: ethtool not found in system path\nerror execution phase wait-control-plane: couldn't initialize a Kubernetes cluster", "stderr_lines": ["\t[WARNING FileExisting-ethtool]: ethtool not found in system path", "error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster"], "stdout": "[init] Using Kubernetes version: v1.13.5\n[preflight] Running pre-flight checks\n[preflight] Pulling images required for setting up a Kubernetes cluster\n[preflight] This might take a minute or two, depending on the speed of your internet connection\n[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'\n[kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n[kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n[kubelet-start] Activating the kubelet service\n[certs] Using certificateDir folder \"/etc/kubernetes/ssl\"\n[certs] Generating \"front-proxy-ca\" certificate and key\n[certs] Generating \"front-proxy-client\" certificate and key\n[certs] Generating \"ca\" certificate and key\n[certs] Generating \"apiserver\" certificate and key\n[certs] apiserver serving cert is signed for DNS names [ks-allinone kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost ks-allinone] and IPs [10.233.0.1 XXX.XX.XX.XXX XXX.XXX.XXX.XXX 10.233.0.1 127.0.0.1 XXX.XXX.XXX.XXX]\n[certs] Generating \"apiserver-kubelet-client\" certificate and key\n[certs] External etcd mode: Skipping etcd/ca certificate authority generation\n[certs] External etcd mode: Skipping etcd/server certificate authority generation\n[certs] External etcd mode: Skipping etcd/peer certificate authority generation\n[certs] External etcd mode: Skipping etcd/healthcheck-client certificate authority generation\n[certs] External etcd mode: Skipping apiserver-etcd-client certificate authority generation\n[certs] Generating \"sa\" key and public key\n[kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n[kubeconfig] Writing \"admin.conf\" kubeconfig file\n[kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n[kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n[kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n[control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n[control-plane] Creating static Pod manifest for \"kube-apiserver\"\n[control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n[control-plane] Creating static Pod manifest for \"kube-scheduler\"\n[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\". This can take up to 5m0s\n[kubelet-check] Initial timeout of 40s passed.\n\nUnfortunately, an error has occurred:\n\ttimed out waiting for the condition\n\nThis error is likely caused by:\n\t- The kubelet is not running\n\t- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)\n\nIf you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:\n\t- 'systemctl status kubelet'\n\t- 'journalctl -xeu kubelet'\n\nAdditionally, a control plane component may have crashed or exited when started by the container runtime.\nTo troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.\nHere is one example how you may list all Kubernetes containers running in docker:\n\t- 'docker ps -a | grep kube | grep -v pause'\n\tOnce you have found the failing container, you can inspect its logs with:\n\t- 'docker logs CONTAINERID'", "stdout_lines": ["[init] Using Kubernetes version: v1.13.5", "[preflight] Running pre-flight checks", "[preflight] Pulling images required for setting up a Kubernetes cluster", "[preflight] This might take a minute or two, depending on the speed of your internet connection", "[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'", "[kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"", "[kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"", "[kubelet-start] Activating the kubelet service", "[certs] Using certificateDir folder \"/etc/kubernetes/ssl\"", "[certs] Generating \"front-proxy-ca\" certificate and key", "[certs] Generating \"front-proxy-client\" certificate and key", "[certs] Generating \"ca\" certificate and key", "[certs] Generating \"apiserver\" certificate and key", "[certs] apiserver serving cert is signed for DNS names [ks-allinone kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost ks-allinone] and IPs [10.233.0.1 XXX.XXX.XXX.XXX XXX.XXX.XXX 10.233.0.1 127.0.0.1 XXX.XXX.XXX.XXX]", "[certs] Generating \"apiserver-kubelet-client\" certificate and key", "[certs] External etcd mode: Skipping etcd/ca certificate authority generation", "[certs] External etcd mode: Skipping etcd/server certificate authority generation", "[certs] External etcd mode: Skipping etcd/peer certificate authority generation", "[certs] External etcd mode: Skipping etcd/healthcheck-client certificate authority generation", "[certs] External etcd mode: Skipping apiserver-etcd-client certificate authority generation", "[certs] Generating \"sa\" key and public key", "[kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"", "[kubeconfig] Writing \"admin.conf\" kubeconfig file", "[kubeconfig] Writing \"kubelet.conf\" kubeconfig file", "[kubeconfig] Writing \"controller-manager.conf\" kubeconfig file", "[kubeconfig] Writing \"scheduler.conf\" kubeconfig file", "[control-plane] Using manifest folder \"/etc/kubernetes/manifests\"", "[control-plane] Creating static Pod manifest for \"kube-apiserver\"", "[control-plane] Creating static Pod manifest for \"kube-controller-manager\"", "[control-plane] Creating static Pod manifest for \"kube-scheduler\"", "[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\". This can take up to 5m0s", "[kubelet-check] Initial timeout of 40s passed.", "", "Unfortunately, an error has occurred:", "\ttimed out waiting for the condition", "", "This error is likely caused by:", "\t- The kubelet is not running", "\t- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)", "", "If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:", "\t- 'systemctl status kubelet'", "\t- 'journalctl -xeu kubelet'", "", "Additionally, a control plane component may have crashed or exited when started by the container runtime.", "To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.", "Here is one example how you may list all Kubernetes containers running in docker:", "\t- 'docker ps -a | grep kube | grep -v pause'", "\tOnce you have found the failing container, you can inspect its logs with:", "\t- 'docker logs CONTAINERID'"]}
NO MORE HOSTS LEFT *****************************************************************************************************************************************************************************
PLAY RECAP *************************************************************************************************************************************************************************************
ks-allinone : ok=316 changed=47 unreachable=0 failed=1
localhost : ok=1 changed=0 unreachable=0 failed=0
Sunday 03 November 2019 08:14:39 -0800 (0:05:06.094) 0:07:48.224 *******
===============================================================================
kubernetes/master : kubeadm | Initialize first master --------------------------------------------------------------------------------------------------------------------------------- 306.09s
container-engine/docker : Docker | pause while Docker restarts ------------------------------------------------------------------------------------------------------------------------- 10.13s
container-engine/docker : ensure docker packages are installed -------------------------------------------------------------------------------------------------------------------------- 8.55s
etcd : wait for etcd up ----------------------------------------------------------------------------------------------------------------------------------------------------------------- 6.49s
etcd : Configure | Check if etcd cluster is healthy ------------------------------------------------------------------------------------------------------------------------------------- 5.48s
kubernetes/preinstall : Update package management cache (APT) --------------------------------------------------------------------------------------------------------------------------- 3.87s
container-engine/docker : docker login -------------------------------------------------------------------------------------------------------------------------------------------------- 3.72s
container-engine/docker : Ensure old versions of Docker are not installed. | Debian ----------------------------------------------------------------------------------------------------- 3.16s
download : Download items --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1.80s
etcd : reload etcd ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1.75s
kubernetes/preinstall : Install packages requirements ----------------------------------------------------------------------------------------------------------------------------------- 1.70s
container-engine/docker : Docker | reload docker ---------------------------------------------------------------------------------------------------------------------------------------- 1.57s
download : file_download | Download item ------------------------------------------------------------------------------------------------------------------------------------------------ 1.51s
bootstrap-os : Assign inventory name to unconfigured hostnames (non-CoreOS and Tumbleweed) ---------------------------------------------------------------------------------------------- 1.28s
download : Sync container --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1.23s
kubernetes/node : install | Copy kubelet binary from download dir ----------------------------------------------------------------------------------------------------------------------- 1.21s
kubernetes/master : Install | Copy kubectl binary from download dir --------------------------------------------------------------------------------------------------------------------- 1.21s
gather facts from all instances --------------------------------------------------------------------------------------------------------------------------------------------------------- 1.10s
download : Sync container --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1.02s
container-engine/docker : ensure docker-ce repository public key is installed ----------------------------------------------------------------------------------------------------------- 1.01s
failed!
Expected behavior(预期行为) A clear and concise description of what you expected to happen.
Successful installation.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 18 (15 by maintainers)
Front end code will be public in a couple of weeks.
ok, we are discussing the next plan about how to deliver the package.
2.1.0-dev is close to GA, so you can download to try it now.
@shinebayar-g Hi, I recommend you to install 2.1.0-dev, all of images have been migrated to DockerHub so the download would be fast than 2.0.2, also the resource requirement is lower, using following command to get started: