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

moving rollbacks folder

Browse Source 
adjust links for folder move

Added troubleshooting of rke

Added clarification of rke version for troubleshooting

Update _index.md

moving rollbacks folder

moving rollbacks folder

moving rollbacks folder
This commit is contained in:
Mark Bishop
2018-08-01 15:49:48 -07:00
committed by Denise
parent e35291f71e
commit efb70142c1
5 changed files with 20 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/v0.1.x/en/installation/etcd-snapshots/_index.md
+3 -3
View File
@@ -221,13 +221,13 @@ nginx-65899c769f-qkhml 1/1 Running 0 17s
## Troubleshooting
As of _v0.1.8_ and below, 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:
As of **v0.1.8** and below, 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.
The rke-bundle-cert container is usually 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.
@@ -238,5 +238,5 @@ 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 _v0.1.9_, the **rke-bundle-cert** container is removed on both success and
As of **v0.1.9**, 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.