Unable to create rke2 cluster

[gcasale82]

Hi all ,
I’m trying to provision a RKE2 cluster from rancher to harvester but it remains stuck at : Configuring bootstrap node(s) mycl-pool1-6bf5854c64-fz6lm: waiting for agent to check in and apply initial plan.
The deployment is behind a proxy but I set agent env variables
HTTP_PROXY=hxxp://172.16.189.3:3128
HTTPS_PROXY=hxxp://172.16.189.3:3128
NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,cattle-system.svc,192.168.0.0/16,172.16.0.0/12,.svc,.cluster.local,.0,.1,.2,.3,.4,.5,.6,.7,.8,.9

During the creation I see these messages in the logs :
Mar 02 16:27:00 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Mar 02 16:27:25 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Mar 02 16:27:30 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Mar 02 16:27:35 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Mar 02 16:27:40 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Mar 02 16:27:45 mycl-pool1-d6a71d8d-pxhvr cloud-init[1322]: [ERROR] Error while connecting to Rancher to verify CA necessity. Sleeping for 5 seconds and trying again.
Below some screenshot:

1 hosted at ImgBB

2 hosted at ImgBB

hxxps://ibb.co/pJ1pV0p
hxxps://ibb.co/qNM8bcT
do you have any suggestion ?
https masquerade as hxxps for avoid errors in opening the topic

[qrKourier]

I seem to be experiencing this same issue with Rancher 2.7.1 and Harvester 1.1.1.

I get this error when I try to build an RKE2 cluster with Harvester as cloud provider.

waiting for viable init node

The nodes are launched, but the console only shows a cloud-init error until the pool is eventually deleted. Wash, rinse, repeat.How can I diagnose the node condition that Rancher is waiting for?

I used the Tumbleweed minimal cloud image and chose the untagged VM network which I’ve used previously, successfully with the DHCP server in my lab LAN.

I opted-in to deprecated K8s version v1.24.9+rke2r2 because it was necessary to enable Harvester as cloud provider.

[gcasale82]

The rke2 nodes must have connectivity to rancher host and all harvester nodes and Vip.Check proxy exclusion , routing and fw rules.