Added troubleshooting of rke

Added clarification of rke version for troubleshooting
This commit is contained in:
Massimo Cannavo
2018-08-01 10:39:02 -07:00
parent 6da9209a5f
commit 599efad9d2
2 changed files with 52 additions and 2 deletions
@@ -218,3 +218,28 @@ nginx-65899c769f-kcdpr 1/1 Running 0 17s
nginx-65899c769f-pc45c 1/1 Running 0 17s
nginx-65899c769f-qkhml 1/1 Running 0 17s
```
## Troubleshooting
There is an issue with **rke v0.1.8** and below were the **rke-bundle-cert** container
is left over from a failed etcd restore. If you are having an issue with restoring an
**etcd snapshot** then you can do the following on each etcd nodes before attempting to
do another restore:
```
docker container rm --force rke-bundle-cert
```
The rke-bundle-cert container is usally removed when a backup or restore of **etcd** succeeds.
Whenever something goes wrong, the **rke-bundle-cert** container will be left over. You can look
at the logs or inspect the container to see what the issue is.
```
docker container logs --follow rke-bundle-cert
docker container inspect rke-bundle-cert
```
The important thing to note is the mounts of the container and location of the **pki.bundle.tar.gz**.
As of **rke v0.1.9** and above, the **rke-bundle-cert** container is removed on both success and
failure of a restore. To debug any issues, you will need to look at the **logs** generated from rke.