Hi,
I get the following error while registering a ...
# generald
damp-smartphone-29286
08/04/2025, 10:51 AMHi,
I get the following error while registering a node to a newly created cluster
Copy code
time="2025-08-04T10:42:07Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"
time="2025-08-04T10:42:09Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"
time="2025-08-04T10:42:10Z" level=debug msg="Wrote ping"
time="2025-08-04T10:42:11Z" level=info msg="Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered"damp-smartphone-29286
08/04/2025, 10:54 AMI have initiated registration for 3 nodes with the following roles:
• Etcd,controlplane, worker - node 3
• Worker - node 2
• Etcd, controplane - node 1
c
creamy-pencil-82913
08/04/2025, 3:57 PMLog on to the nodes and check the journald log to see why it's failing to register
d
damp-smartphone-29286
08/04/2025, 3:59 PMI see that it is running in docker
damp-smartphone-29286
08/04/2025, 4:00 PMWe are not running as
rancher-agent.servicec
creamy-pencil-82913
08/04/2025, 4:02 PMAre you using RKE? Or k3s/rke2?
creamy-pencil-82913
08/04/2025, 4:02 PMRKE is eol as of August 1...
d
damp-smartphone-29286
08/04/2025, 4:02 PMRKE
damp-smartphone-29286
08/04/2025, 4:03 PMWe are yet to upgrade
damp-smartphone-29286
08/04/2025, 4:03 PMBut the agent I see which is running in docker is having v2.6.12
c
creamy-pencil-82913
08/04/2025, 4:04 PMThat is also super old. Latest is 2.12.
d
damp-smartphone-29286
08/04/2025, 4:05 PMWe have a plan to upgrade it in a couple of weeks
damp-smartphone-29286
08/04/2025, 4:06 PMCan you please give me some hints on how to resolve the above?
damp-smartphone-29286
08/04/2025, 4:08 PMAnd can we upgrade directly from 2.6.12 to 2.12 ?