This message was deleted.
# vsphere
a
This message was deleted.
s
Yes there are 2 ways that you can troubleshoot this the first one are the logs that gets displayed on the vcenter when the vm is getting provisioned other that what you can do is go to the cluster where your rancher UI is deployed and run this command
kubectl logs -f #pod_id -n cattle-system ---> to see the live logs
here the pod id will be of rancher pod as the error you are stuck at "waiting to check in and apply initial plan" that can also mean the nodes have not come up if the nodes are up on vcenter try accessing them and run
kubectl get pods -A
to see if it has started deploying the core pods
Also can you tell , how you created the ubuntu vm template ?
b
just created it manually from a VM
kubectl doesn't seem to be installed on the node - I assumed it would be provisioned onto it with the rke2 provisioner somehow?
the nodes are up, but they don't seem to be doing anything
s
have installed the pre-req on that vmtemplate ?
b
perhaps not 😕 able to point me in the right direction?
s
yes let me
b
I was assuming the rke2 provisioner would manage that somehow
s
first thing is u need a user account in the vsphere to provision nodes
these are the rights of that user that should be present
b
oh I mean, I have that, the nodes get provisioned
but they just sit there
s
for that just validate if you have these packages installed
once you do that
your vm wont get stuck
and makesure clou-init is installed
cloud-init*
also for the downstream nodes you will find the kubeconfig in the /etc/rancher/rke2/rke2.yaml
and kubectl is in /var/lib/rancher/rke2/bin
b
thanks very much
if I install them manually on a node now and then restart it, will it work?
or I have to start from beginning
🙌 1
s
feel free to reach out if you have any queries about this
b
it worked, thank you
💯 1
🙇 1
s
Great