I have four Ubuntu 22 04 VMs running One of them is my RKE w rancher-users #general

Title

acoustic-processor-40872

08/05/2022, 10:56 PM

I have four Ubuntu 22.04 VMs running. One of them is my RKE workstation that has SSH tunneling established to the other three VMs, which serve as my nodes. I’m trying to create an HA RKE Kubernetes cluster so I can install Rancher. I run the

cluster.yml

using rke up. I get the following error.

INFO[0005] [network] Running etcd <-> etcd port checks  
INFO[0005] [network] Checking if host [<node-1>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #1 
INFO[0005] [network] Checking if host [<node-2>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #1 
INFO[0005] [network] Checking if host [<node-3>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #1 
INFO[0005] Image [rancher/rke-tools:v0.1.80] exists on host [<node-3>] 
INFO[0005] Image [rancher/rke-tools:v0.1.80] exists on host [<node-2>] 
INFO[0005] Image [rancher/rke-tools:v0.1.80] exists on host [<node-1>] 
INFO[0005] Starting container [rke-port-checker] on host [<node-3>], try #1 
INFO[0005] Starting container [rke-port-checker] on host [<node-1>], try #1 
INFO[0005] [network] Successfully started [rke-port-checker] container on host [<node-3>] 
INFO[0005] [network] Successfully started [rke-port-checker] container on host [<node-1>] 
INFO[0005] Removing container [rke-port-checker] on host [<node-1>], try #1 
INFO[0005] Starting container [rke-port-checker] on host [<node-2>], try #1 
INFO[0006] [network] Successfully started [rke-port-checker] container on host [<node-2>] 
INFO[0010] Removing container [rke-port-checker] on host [<node-3>], try #1 
INFO[0011] Removing container [rke-port-checker] on host [<node-2>], try #1 
INFO[0015] [network] Checking if host [<node-3>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #2 
INFO[0015] Image [rancher/rke-tools:v0.1.80] exists on host [<node-3>] 
INFO[0015] Starting container [rke-port-checker] on host [<node-3>], try #1 
INFO[0016] [network] Successfully started [rke-port-checker] container on host [<node-3>] 
INFO[0016] [network] Checking if host [<node-2>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #2 
INFO[0016] Image [rancher/rke-tools:v0.1.80] exists on host [<node-2>] 
INFO[0016] Starting container [rke-port-checker] on host [<node-2>], try #1 
INFO[0016] [network] Successfully started [rke-port-checker] container on host [<node-2>] 
INFO[0021] Removing container [rke-port-checker] on host [<node-3>], try #1 
INFO[0021] Removing container [rke-port-checker] on host [<node-2>], try #1 
INFO[0026] [network] Checking if host [<node-3>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #3 
INFO[0026] Image [rancher/rke-tools:v0.1.80] exists on host [<node-3>] 
INFO[0026] Starting container [rke-port-checker] on host [<node-3>], try #1 
INFO[0026] [network] Successfully started [rke-port-checker] container on host [<node-3>] 
INFO[0026] [network] Checking if host [<node-2>] can connect to host(s) [<node-1> <node-2> <node-3>] on port(s) [2379 2380], try #3 
INFO[0026] Image [rancher/rke-tools:v0.1.80] exists on host [<node-2>] 
INFO[0027] Starting container [rke-port-checker] on host [<node-2>], try #1 
INFO[0027] [network] Successfully started [rke-port-checker] container on host [<node-2>] 
INFO[0031] Removing container [rke-port-checker] on host [<node-3>], try #1 
INFO[0032] Removing container [rke-port-checker] on host [<node-2>], try #1 
FATA[0037] [[network] Host [<node-3>] is not able to connect to the following ports: [<node-1>:2379, <node-1>:2380]. Please check network policies and firewall rules]

Running

netstat -at

on four VMS yields…

Node 1

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:6443            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2379            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2380            0.0.0.0:*               LISTEN     
tcp        0      0 localhost:domain        0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:10250           0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN     
tcp        0    240 tom-cruise:ssh          some-ip:60527    ESTABLISHED
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN

Node 2

square-orange-60123

08/05/2022, 10:59 PM

I don’t think we officially support 22.04 yet.

acoustic-processor-40872

08/05/2022, 10:59 PM

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:10250           0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2379            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2380            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:6443            0.0.0.0:*               LISTEN     
tcp        0      0 localhost:domain        0.0.0.0:*               LISTEN     
tcp        0    240 bruce-willis:ssh        ip-2:60514    ESTABLISHED
tcp        0      0 bruce-willis:35906      ip-3:domain      ESTABLISHED
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN

Wait, really?

Which Ubuntu version do you recommend I use?

square-orange-60123

08/05/2022, 11:04 PM

20.04

👍 1

not sure if that’s the root cause of your issues, but it might get you a little closer. If you don’t have any specific network rules setup for those nodes, my guess would be the OS with this info you’ve provided.

👍 2

acoustic-processor-40872

08/05/2022, 11:09 PM

Omg, I will try that! I’ll get back to you!

👍 1

polite-piano-74233

08/06/2022, 12:30 AM

yea 22.04 has been a lot of pain for me with rancher, considering switching back as well

acoustic-processor-40872

08/08/2022, 8:05 PM

IT WORKED!!!!!!

OMGGGGG THANK YOU!!!! I’ve been trying to get this to work for that last 6 days! Switching to Ubuntu 20.04 (LTS) did the trick!!!!!

🎉 1

2 Views

#general Join Slack