rke2-server service start failing due to failed to get unit file state nm-cloud-setup.service: No such file or directory #6418
Replies: 2 comments 13 replies
-
No, that's not what's happening. You're misreading the logs - the ExecStartPre that checks to ensure the Check the rest of the logs to see why the |
Beta Was this translation helpful? Give feedback.
-
|
There are going to be a lot of errors until the apiserver comes up. You are welcome to zip up the logs and upload them here, but I'm not able to hold your hand through troubleshooting an unspecified problem. |
Beta Was this translation helpful? Give feedback.
-
|
I have fixed the rke2-server.service issue, now it is running however, when I did "export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin" as per rke2 doc however when I run kubectl get nodes, it says "kubectl not found" I can see the kubectl is located under /usr/local/bin/kubectl In addition to this, I have kubeconfig file configured as below: |
Beta Was this translation helpful? Give feedback.
-
|
RKE2 does not provide
ok, so put that in your path? |
Beta Was this translation helpful? Give feedback.
-
|
Finally, it is working, It was mix of permission issue on the bin/kubectl and rke2.yaml, thanks for your help @brandond |
Beta Was this translation helpful? Give feedback.
-
May be you missed the last comment, it is all working. to add another nodes as rke2-server to join the cluster, do I have to instrall the followings:
or just install rke2 binary which is rke2-.linux-amd64.tar.gz on other controlplane node so that they can be treated as rke2-server. Please advice |
Beta Was this translation helpful? Give feedback.
-
|
to add another nodes as rke2-server to join the cluster, do I have to instrall the followings:
or just install rke2 binary which is rke2-.linux-amd64.tar.gz on other controlplane node so that they can be treated as rke2-server. Please advice |
Beta Was this translation helpful? Give feedback.
-
|
If you don't have an external registry mirror available, all the nodes need images to be available locally via tarballs. You should put the same set of images on all nodes. Alternately, you can enable the embedded registry mirror to allow sharing images between nodes. This is not currently covered in the RKE2 docs, but you can reference the k3s docs at https://docs.k3s.io/installation/registry-mirror |
Beta Was this translation helpful? Give feedback.
-
|
Do I have to install only rke2-images-core.linux-amd64.tar.gz, rke2-.linux-amd64.tar.gz (rke2 binary) on other controlplane nodes in AirGap environment. Same thing with RKE2-Agent, I have to install the images and rke2 binary. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
As I said, all the nodes need all the images. Why wouldn't you need the CNI on agents? |
Beta Was this translation helpful? Give feedback.
-
I have downloaded the cilium images, rke2-core-linux-amd64 and rke2.linux-amd64 on my controlplane node and installed rke2 binary (rke2.linux-amd64), at somehow I have followed the rke2 instructions for Ari-Gap environment however rke2-server service is getting failed due to the below:
Process: 1234566 ExecStart=/usr/local/bin/rke2 server (code=exited, status=1/FAILURE)
Process: 1234566 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
rke2-server service start failing due to failed to get unit file state nm-cloud-setup.service: No such file or directory
I have checked the service nm-cloud-setup.service does not exist at all, not sure why it is still pointing to this service. I tried to google it but could not find the correct answer.
Any suggestion would be great
Beta Was this translation helpful? Give feedback.
All reactions