https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
a
Not a static pod, standalone container
f
Yeah, I figured. Now I tried manually running the rancher agent in the hopes that it would re-spawn the missing components. Now it looks like it's trying to pull from the wrong repo: 
unauthorized to access repository: internal/rancher/rancher-agent
but I don't know where it gets that from. There's no private repos configured on the cluster.
a
Did you create this cluster from rancher? What kind of cluster?
f
Yes, RKE1
Copy code
time="2023-06-05T19:25:00Z" level=info msg="Connecting to <wss://redacted.example.com/v3/connect> with token starting with <TOKEN>"
time="2023-06-05T19:25:00Z" level=info msg="Connecting to proxy" url="<wss://redacted.example.com/v3/connect>"
time="2023-06-05T19:25:00Z" level=error msg="Remotedialer proxy error" error="Error response from daemon: unauthorized: unauthorized to access repository: internal/rancher/rancher-agent, action: pull: unauthorized to access repository: internal/rancher/rancher-agent, action: pull"
^ logs from rancher-agent container
a
Custom cluster or IaaS?
f
Custom. vsphere node provider
Which means not custom, I guess 😄 but onprem vmware cluster
a
If it's using the vSphere node driver I'd just delete the node and let rancher recreate it
f
Would have done that, if it wasn't my only cp/etcd node....
will rancher be able to re-create that from snapshot? No I guess, because re-creation of a cp node will not have any cluster to join?
a
Add another node. Remove the broken one
f
tried that. but adding the extra node doesn't work... which.. I guess is the catch22.. -> there's no apiserver on which to register the new node:
2 Views
Open in Slack
PreviousNext
Powered by