https://rancher.com/ logo
#rke2
Title
# rke2
f

future-monitor-61871

01/20/2023, 9:23 PM
Attempting to add agent nodes to an rke2 v1.25.5+rke2r1, and the token which was provided for the original cluster is not being accepted by the agents. Do I need to extract the agent token to add new agents or what? "Waiting to retrieve agent configuration; server is not ready: Node password rejected, duplicate hostname or contents of '/etc/rancher/node/password' may not match server node-passwd entry, try enabling a unique node name with the --with-node-id flag""
c

creamy-pencil-82913

01/20/2023, 9:33 PM
that’s not the token then
is there still a node in the cluster with that same hostname? if you do
kubectl get node
?
the node password is not the same thing as the token
See the bit below https://docs.rke2.io/advanced#node-labels-and-taints about agent node registration
f

future-monitor-61871

01/20/2023, 9:38 PM
ok, that gives me a bit more to go on. No there isn't a node w/ that name in the kubectl get nodes but perhaps we had an old node-password.rk2 secret hanging about
757 Views