public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-19 03:17:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add first RKE provisioning errors troubleshooting

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2019-07-16 19:47:32 +02:00
committed by Denise
parent 8c5f1105e1
commit 60d0c7014b
2 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/troubleshooting/_index.md
+1
View File
@@ -4,3 +4,4 @@ weight: 400
---
* [SSH Connectivity Errors]({{< baseurl >}}/rke/latest/en/troubleshooting/ssh-connectivity-errors/)
* [Provisioning Errors]({{< baseurl >}}/rke/latest/en/troubleshooting/provisioning-errors/)
content/rke/latest/en/troubleshooting/provisioning-errors/_index.md
+19
View File
@@ -0,0 +1,19 @@
---
title: Provisioning Errors
weight: 200
---
### Failed to get job complete status
Most common reason for this error is that a node is having issues that block the deploy job from completing successfully. See [Get node conditions]({{< baseurl >}}/rancher/v2.x/en/troubleshooting/kubernetes-resources/#get-node-conditions) how to check node conditions.
You can also retrieve the log from the job to see if it has an indication of the error, make sure you replace `rke-network-plugin-deploy-job` with the job name from the error:
Example command to get logs for error `Failed to get job complete status for job rke-network-plugin-deploy-job`:
```
kubectl -n kube-system get pods -l job-name=rke-network-plugin-deploy-job --no-headers -o custom-columns=NAME:.metadata.name | xargs -L1 kubectl -n kube-system logs
```
### Failed to apply the ServiceAccount needed for job execution
Because this action requires connectivity from the host running `rke up` to the controlplane nodes, this is usually caused by incorrect proxy configuration on the host running `rke up`. The message printed after this error usually is the response from the proxy that is blocking the request. Please verify the `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables are correctly configured, especially `NO_PROXY` if the host cannot reach the controlplane nodes via the configured proxy. (this IP range then needs to be added to `NO_PROXY` to make it work)