https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
i
Same error for me
c
Did you get anywhere with it @important-journalist-46296?
f
I did docker restart kubelet on node, that helped
g
Are you using SSH_AUTH_SOCK.. I faced the same issue with RKE terraform provider 1.4.2 when using SSH_AUTH_SOCK.. Using the ssh key instead of socket solved the issue
c
Rancher's done all the provisioning, we haven't done anything manual with rke
g
Are you using cluster.yml file and rke up command to build the cluster or terraform scripts
c
Neither, it's a rancher provisioned cluster. the machines are registered with the docker registration command
Soryr I think I see what you mean. The rancher ui has basically built the cluster.yml. ssh_agent_auth is set to false in there
g
If possible try using the actual ssh key instead of agent .It fixed the issue for me
c
How would I do that? I'm not entirely sure how rancher actually tries to connect to do the upgrade
g
We were using terraform and there it had an option for ssh_file_path to specify location of the ssh key
I am not sure how provisioning from rancher ui works
Since ssh_agent_auth is set to false you must be providing the ssh_key_file otherwise RKE will have no access to nodes and won't be able to build the cluster
c
the rancher ui has a registration command that runs a docker container with a token to talk back to the rancher server - as far as i'm aware i haven't provided it with a key
Open in Slack
PreviousNext
Powered by