You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error ```
W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration! 10.10.1.2:22 [preflight] Running pre-flight checks 10.10.1.2:22 [WARNING FileExisting-ethtool]: ethtool not found in system path 10.10.1.2:22 [preflight] Reading configuration from the cluster... 10.10.1.2:22 [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml' 10.10.1.2:22 W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0 10.10.1.2:22 error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node 10.10.1.2:22 To see the stack trace of this error execute with --v=5 or higher
2024-04-24T10:09:37 error Applied to cluster error: failed to join node 10.10.1.2:22 run command kubeadm join --config=/root/.sealos/default/etc/kubeadm-join-node.yaml -v 0 on 10.10.1.2:22, output: W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
[preflight] Running pre-flight checks
[WARNING FileExisting-ethtool]: ethtool not found in system path
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
To see the stack trace of this error execute with --v=5 or higher
, error: Process exited with status 1,
Error: failed to join node 10.10.1.2:22 run command `kubeadm join --config=/root/.sealos/default/etc/kubeadm-join-node.yaml -v 0` on 10.10.1.2:22, output: W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
[preflight] Running pre-flight checks
[WARNING FileExisting-ethtool]: ethtool not found in system path
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
To see the stack trace of this error execute with --v=5 or higher
, error: Process exited with status 1,
3. run `hostnamectl` on 10.10.1.1 and 10.10.1.2, they have same hostname settings
```Static hostname: n/a
Transient hostname: lvscare.node.ip
Icon name: computer-vm
Chassis: vm
Machine ID: xxxxxxx
Boot ID: xxxxxx
Virtualization: kvm
Operating System: Ubuntu 20.04.6 LTS
Kernel: Linux 5.4.0-56-generic
Architecture: x86-64
看这里 error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
看这里 error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
Sealos Version
v4.3.7
How to reproduce the bug?
sealos add --nodes 10.10.1.1,10.10.1.2
W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
10.10.1.2:22 [preflight] Running pre-flight checks
10.10.1.2:22 [WARNING FileExisting-ethtool]: ethtool not found in system path
10.10.1.2:22 [preflight] Reading configuration from the cluster...
10.10.1.2:22 [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
10.10.1.2:22 W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
10.10.1.2:22 error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
10.10.1.2:22 To see the stack trace of this error execute with --v=5 or higher
2024-04-24T10:09:37 error Applied to cluster error: failed to join node 10.10.1.2:22 run command
kubeadm join --config=/root/.sealos/default/etc/kubeadm-join-node.yaml -v 0
on 10.10.1.2:22, output: W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration![preflight] Running pre-flight checks
[WARNING FileExisting-ethtool]: ethtool not found in system path
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
To see the stack trace of this error execute with --v=5 or higher
, error: Process exited with status 1,
Error: failed to join node 10.10.1.2:22 run command `kubeadm join --config=/root/.sealos/default/etc/kubeadm-join-node.yaml -v 0` on 10.10.1.2:22, output: W0424 10:09:36.876147 2123 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
[preflight] Running pre-flight checks
[WARNING FileExisting-ethtool]: ethtool not found in system path
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0424 10:09:37.338544 2123 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
error execution phase kubelet-start: a Node with name "lvscare.node.ip" and status "Ready" already exists in the cluster. You must delete the existing Node or change the name of this new joining Node
To see the stack trace of this error execute with --v=5 or higher
, error: Process exited with status 1,
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
Additional information
No response
The text was updated successfully, but these errors were encountered: