Open sumlittle opened 5 days ago
v3.1.1
rocky linux 9.4
apiVersion: kubekey.kubesphere.io/v1alpha2 kind: Cluster metadata: name: sample spec: hosts: - {name: k8s1, address: 192.168.139.129, internalAddress: 192.168.139.129, user: root, password: "admin"} - {name: k8s2, address: 192.168.139.139, internalAddress: 192.168.139.139, user: root, password: "admin"} - {name: k8s3, address: 192.168.139.149, internalAddress: 192.168.139.149, user: root, password: "admin"} roleGroups: etcd: - k8s1 - k8s2 - k8s3 control-plane: - k8s1 - k8s2 - k8s3 worker: - k8s1 - k8s2 - k8s3 controlPlaneEndpoint: ## Internal loadbalancer for apiservers internalLoadbalancer: haproxy domain: lb.kubesphere.local address: "" port: 6443 kubernetes: version: v1.28.8 clusterName: cluster.local autoRenewCerts: true containerManager: containerd etcd: type: kubekey network: plugin: calico kubePodsCIDR: 10.233.64.0/18 kubeServiceCIDR: 10.233.0.0/18 ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni multusCNI: enabled: false registry: privateRegistry: "" namespaceOverride: "" registryMirrors: [] insecureRegistries: [] addons: []
ε¨ζ§θ‘./kk create cluster -f k8s-v1288.yamlεζ§θ‘δΊδΈδΌοΌεηζ₯ι
19:52:08 CST message: [k8s1] etcd health check failed: Failed to exec command: sudo -E /bin/bash -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-k8s1.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-k8s1-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://192.168.139.129:2379,https://192.168.139.139:2379,https://192.168.139.149:2379 cluster-health | grep -q 'cluster is healthy'" Error: client: etcd cluster is unavailable or misconfigured; error #0: client: endpoint https://192.168.139.149:2379 exceeded header timeout ; error #1: client: endpoint https://192.168.139.139:2379 exceeded header timeout ; error #2: client: endpoint https://192.168.139.129:2379 exceeded header timeout error #0: client: endpoint https://192.168.139.149:2379 exceeded header timeout error #1: client: endpoint https://192.168.139.139:2379 exceeded header timeout error #2: client: endpoint https://192.168.139.129:2379 exceeded header timeout: Process exited with status 1 19:52:08 CST retry: [k8s1] 19:52:19 CST message: [k8s1] etcd health check failed: Failed to exec command: sudo -E /bin/bash -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-k8s1.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-k8s1-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://192.168.139.129:2379,https://192.168.139.139:2379,https://192.168.139.149:2379 cluster-health | grep -q 'cluster is healthy'" Error: client: etcd cluster is unavailable or misconfigured; error #0: client: endpoint https://192.168.139.129:2379 exceeded header timeout ; error #1: client: endpoint https://192.168.139.149:2379 exceeded header timeout ; error #2: client: endpoint https://192.168.139.139:2379 exceeded header timeout error #0: client: endpoint https://192.168.139.129:2379 exceeded header timeout error #1: client: endpoint https://192.168.139.149:2379 exceeded header timeout error #2: client: endpoint https://192.168.139.139:2379 exceeded header timeout: Process exited with status 1 19:52:19 CST retry: [k8s1] 19:52:31 CST message: [k8s1] etcd health check failed: Failed to exec command: sudo -E /bin/bash -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-k8s1.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-k8s1-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://192.168.139.129:2379,https://192.168.139.139:2379,https://192.168.139.149:2379 cluster-health | grep -q 'cluster is healthy'" Error: client: etcd cluster is unavailable or misconfigured; error #0: client: endpoint https://192.168.139.149:2379 exceeded header timeout ; error #1: client: endpoint https://192.168.139.139:2379 exceeded header timeout ; error #2: client: endpoint https://192.168.139.129:2379 exceeded header timeout error #0: client: endpoint https://192.168.139.149:2379 exceeded header timeout error #1: client: endpoint https://192.168.139.139:2379 exceeded header timeout
No response
What is version of KubeKey has the issue?
v3.1.1
What is your os environment?
rocky linux 9.4
KubeKey config file
A clear and concise description of what happend.
ε¨ζ§θ‘./kk create cluster -f k8s-v1288.yamlεζ§θ‘δΊδΈδΌοΌεηζ₯ι
Relevant log output
Additional information
No response