kubesphere
kubesphere copied to clipboard
When installing the cluster, the output "/usr/local/bin/kubectl: No such file or directory" error
English only!
注意!GitHub Issue 仅支持英文,中文 Issue 请在 论坛 提交。
General remarks
Please delete this section including header before submitting
This form is to report installation issues. For general usage questions you can refer to KubeSphere Documentation or join our Slack channel KubeSphere-users
What's your question
./kk create config --with-kubernetes v1.22.10 --with-kubesphere v3.3.0
./kk create cluster -f config-sample.yaml
Environment: OS & Hardware Information Linux version 3.10.0-862.2.3.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Wed May 9 18:05:47 UTC 2018 2C / 4G
Important: You must describe your environment clearly, e.g. VMware or Bare Metal, CentOS 7.5, 8 C / 16 G (If you install on Linux), Or Kubernetes v1.16 (If you install on K8s).
Error logs or message (Attach logs or screenshot)
...
11:13:38 CST success: [master]
11:13:38 CST success: [node1]
11:13:38 CST [ConfigureOSModule] configure the ntp server for each node
11:13:38 CST skipped: [node1]
11:13:38 CST skipped: [master]
11:13:38 CST [KubernetesStatusModule] Get kubernetes cluster status
11:13:38 CST stdout: [master]
v1.26.2
11:13:38 CST stdout: [master]
/bin/bash: /usr/local/bin/kubectl: No such file or directory
11:13:38 CST message: [master]
get kubernetes cluster info failed: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubectl --no-headers=true get nodes -o custom-columns=:metadata.name,:status.nodeInfo.kubeletVersion,:status.addresses"
/bin/bash: /usr/local/bin/kubectl: No such file or directory: Process exited with status 127
11:13:38 CST retry: [master]
11:13:43 CST stdout: [master]
v1.26.2
11:13:43 CST stdout: [master]
/bin/bash: /usr/local/bin/kubectl: No such file or directory
11:13:43 CST message: [master]
get kubernetes cluster info failed: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubectl --no-headers=true get nodes -o custom-columns=:metadata.name,:status.nodeInfo.kubeletVersion,:status.addresses"
/bin/bash: /usr/local/bin/kubectl: No such file or directory: Process exited with status 127
11:13:43 CST retry: [master]
11:13:49 CST stdout: [master]
v1.26.2
11:13:49 CST stdout: [master]
/bin/bash: /usr/local/bin/kubectl: No such file or directory
11:13:49 CST message: [master]
get kubernetes cluster info failed: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubectl --no-headers=true get nodes -o custom-columns=:metadata.name,:status.nodeInfo.kubeletVersion,:status.addresses"
/bin/bash: /usr/local/bin/kubectl: No such file or directory: Process exited with status 127
11:13:49 CST failed: [master]
error: Pipeline[CreateClusterPipeline] execute failed: Module[KubernetesStatusModule] exec failed:
failed: [master] [GetClusterStatus] exec failed after 3 retires: get kubernetes cluster info failed: Failed to exec command: sudo -E /bin/bash -c "/usr/local/bin/kubectl --no-headers=true get nodes -o custom-columns=:metadata.name,:status.nodeInfo.kubeletVersion,:status.addresses"
/bin/bash: /usr/local/bin/kubectl: No such file or directory: Process exited with status 127
Installer Version --with-kubernetes v1.22.10 --with-kubesphere v3.3.0
e.g. v2.1.0, v2.1.1, v3.0.0
Installer Version --with-kubernetes v1.24.8 --with-kubesphere v3.3.2 This version also has the same issue. Have you resolved it?
same issue
Same here, using openSUSE Leap 15.4
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.