This message was deleted.
# generala
adamant-kite-43734
08/03/2023, 2:00 PMThis message was deleted.
✅ 1
s
swift-eve-48927
08/03/2023, 3:36 PMHere are the provisioning logs for one of the rke2 cluster. If everything else succeeds, what would stop the cluster agent from connecting?
Copy code
[INFO ] waiting for infrastructure ready
[INFO ] waiting for at least one control plane, etcd, and worker node to be registered
[INFO ] waiting for viable init node
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for agent to check in and apply initial plan
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for probes: calico, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for probes: calico, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for probes: calico
[INFO ] configuring bootstrap node(s) test-rke-pool1-7f995b8df9-xvm7d: waiting for cluster agent to connectswift-eve-48927
08/03/2023, 7:27 PMI seem to be having issues with the tunnel and/or websocket connections between downstream nodes and the Rancher Server.
journalctl -u rke2-server Copy code
level=info msg="Stopped tunnel to 127.0.0.1:9345"
level=info msg="Proxy done" err="context canceled" url="<wss://127.0.0.1:9345/v1-rke2/connect>"
level=info msg="Connecting to proxy" url="<wss://10.3.3.126:9345/v1-rke2/connect>"
level=info msg="error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF" Copy code
[INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF"unable to decode an event from the watch stream: tunnel disconnect"c
creamy-pencil-82913
08/03/2023, 7:30 PMthose message on the rke2 side are normal.
creamy-pencil-82913
08/03/2023, 7:30 PMhas nothing to do with a tunnel to rancher, those are about internal REK2 tunnels between cluster nodes. The rancher stuff all runs in pods, you won’t find anything about rancher in the rke2 service logs.
s
swift-eve-48927
08/03/2023, 7:32 PMGotcha. Thank you, I’ll keep looking.
swift-eve-48927
08/03/2023, 7:40 PMI’m seeing the cattle-cluster-agent pod is in a
Pending Copy code
Warning FailedScheduling 18m (x10 over 68m) default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {<http://node.cloudprovider.kubernetes.io/uninitialized|node.cloudprovider.kubernetes.io/uninitialized>: true}. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..c
creamy-pencil-82913
08/03/2023, 7:44 PMwell it’s certainly an issue with the cloud provider. Have you looked at the cloud provider pod logs to see why it’s not working?
creamy-pencil-82913
08/03/2023, 7:44 PMthe pod on the downstream cluster, not on the harvester side
s
swift-eve-48927
08/03/2023, 7:52 PMAhhh, ok. The issue is clear. I didn’t realize the downstream nodes needed to be able to reach the Harvester network. I have the Harvester cluster and downstream nodes deployed in separate subnets with no routes between, so I see I need to rethink how I have things set up. Thank you for pointing me in the right direction!
c
creamy-pencil-82913
08/03/2023, 8:00 PMyes, the cloud controller manager needs to actually be able to talk to the cloud provider
349 Views