Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to install k3s v.1.24.7 cluster on Ubuntu 22.04 LTS #1945

Open
niconical opened this issue Aug 5, 2023 · 1 comment
Open

failed to install k3s v.1.24.7 cluster on Ubuntu 22.04 LTS #1945

niconical opened this issue Aug 5, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@niconical
Copy link

niconical commented Aug 5, 2023

What is version of KubeKey has the issue?

kk version: &version.Info{Major:"3", Minor:"0", GitVersion:"v3.0.10", GitCommit:"3e381c6d5556117d132326b58c5177e0b0e839b6", GitTreeState:"clean", BuildDate:"2023-07-28T06:08:59Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

What is your os environment?

Ubuntu 22.04 LTS

KubeKey config file

No response

A clear and concise description of what happend.

I tried to use Kubekey to install the K3S cluster on Ubuntu 22.04 and failed. I used the following command to install:
sudo ./kk create cluster --with-kubernetes v1.24.7-k3s

Then report an error:

21:53:15 CST [GreetingsModule] Greetings
21:53:16 CST message: [VM-0-4-ubuntu]
Greetings, KubeKey!
21:53:16 CST success: [VM-0-4-ubuntu]
21:53:16 CST [K3sNodeBinariesModule] Download installation binaries
21:53:16 CST message: [localhost]
downloading amd64 k3s v1.24.7 ...
21:53:16 CST message: [localhost]
downloading amd64 helm v3.9.0 ...
21:53:17 CST message: [localhost]
downloading amd64 kubecni v1.2.0 ...
21:53:17 CST message: [localhost]
downloading amd64 etcd v3.4.13 ...
21:53:17 CST message: [localhost]
downloading amd64 calicoctl v3.23.2 ...
21:53:17 CST success: [LocalHost]
21:53:17 CST [ConfigureOSModule] Get OS release
21:53:17 CST success: [VM-0-4-ubuntu]
21:53:17 CST [ConfigureOSModule] Prepare to init OS
21:53:17 CST success: [VM-0-4-ubuntu]
21:53:17 CST [ConfigureOSModule] Generate init os script
21:53:17 CST success: [VM-0-4-ubuntu]
21:53:17 CST [ConfigureOSModule] Exec init os script
21:53:18 CST stdout: [VM-0-4-ubuntu]
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.ip_forward = 1
kernel.sysrq = 1
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.lo.disable_ipv6 = 0
kernel.printk = 5
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_local_reserved_ports = 30000-32767
net.core.netdev_max_backlog = 65535
net.core.rmem_max = 33554432
net.core.wmem_max = 33554432
net.core.somaxconn = 32768
net.ipv4.tcp_max_syn_backlog = 1048576
net.ipv4.neigh.default.gc_thresh1 = 512
net.ipv4.neigh.default.gc_thresh2 = 2048
net.ipv4.neigh.default.gc_thresh3 = 4096
net.ipv4.tcp_retries2 = 15
net.ipv4.tcp_max_tw_buckets = 1048576
net.ipv4.tcp_max_orphans = 65535
net.ipv4.udp_rmem_min = 131072
net.ipv4.udp_wmem_min = 131072
net.ipv4.conf.all.arp_accept = 1
net.ipv4.conf.default.arp_accept = 1
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.default.arp_ignore = 1
vm.max_map_count = 262144
vm.swappiness = 0
vm.overcommit_memory = 0
fs.inotify.max_user_instances = 524288
fs.inotify.max_user_watches = 524288
fs.pipe-max-size = 4194304
fs.aio-max-nr = 262144
kernel.pid_max = 65535
kernel.watchdog_thresh = 5
kernel.hung_task_timeout_secs = 5
21:53:18 CST success: [VM-0-4-ubuntu]
21:53:18 CST [ConfigureOSModule] configure the ntp server for each node
21:53:18 CST skipped: [VM-0-4-ubuntu]
21:53:18 CST [StatusModule] Get k3s cluster status
21:53:19 CST stdout: [VM-0-4-ubuntu]
v1.24.7+k3s1
21:53:19 CST stdout: [VM-0-4-ubuntu]
K10e4d874d4a3746c9adf73495171e001842e5dbbeadf4ede2c840468a3b07b9ab3::server:0ec6e74ea0a04348b6c2822e13de4e15
21:53:19 CST stdout: [VM-0-4-ubuntu]
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
21:53:19 CST message: [VM-0-4-ubuntu]
get k3s 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" 
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: Process exited with status 1
21:53:19 CST retry: [VM-0-4-ubuntu]
21:53:24 CST stdout: [VM-0-4-ubuntu]
v1.24.7+k3s1
21:53:24 CST stdout: [VM-0-4-ubuntu]
K10e4d874d4a3746c9adf73495171e001842e5dbbeadf4ede2c840468a3b07b9ab3::server:0ec6e74ea0a04348b6c2822e13de4e15
21:53:24 CST stdout: [VM-0-4-ubuntu]
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
21:53:24 CST message: [VM-0-4-ubuntu]
get k3s 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" 
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: Process exited with status 1
21:53:24 CST retry: [VM-0-4-ubuntu]
21:53:29 CST stdout: [VM-0-4-ubuntu]
v1.24.7+k3s1
21:53:29 CST stdout: [VM-0-4-ubuntu]
K10e4d874d4a3746c9adf73495171e001842e5dbbeadf4ede2c840468a3b07b9ab3::server:0ec6e74ea0a04348b6c2822e13de4e15
21:53:30 CST stdout: [VM-0-4-ubuntu]
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
21:53:30 CST message: [VM-0-4-ubuntu]
get k3s 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" 
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: Process exited with status 1
21:53:30 CST failed: [VM-0-4-ubuntu]
error: Pipeline[K3sCreateClusterPipeline] execute failed: Module[StatusModule] exec failed: 
failed: [VM-0-4-ubuntu] [GetClusterStatus] exec failed after 3 retries: get k3s 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" 
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: Process exited with status 1

Relevant log output

No response

Additional information

amd64 arch

@niconical niconical added the bug Something isn't working label Aug 5, 2023
@niconical niconical changed the title failed to install k3s cluster on Ubuntu 22.04 LTS failed to install k3s v.1.24.7 cluster on Ubuntu 22.04 LTS Aug 5, 2023
@GunniBusch
Copy link

any updates? It still does this, and no new k3s versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants