public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +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/rancher/v2.x/en/upgrades/_index.md
+9 -3
View File
@@ -9,9 +9,15 @@ Each new version of Rancher 2.x.x supports upgrades from previous versions of Ra
Complete one of the upgrade procedures below based on your Rancher installation:
- [Single Node Upgrade](./single-node-upgrade/)
- [High Availability Upgrade](./ha-server-upgrade/)
- [Air Gap Upgrade](./air-gap-upgrade/)
- [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/single-node-upgrade)
- [High Availability Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/ha-server-upgrade)
- [Air Gap Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/air-gap-upgrade)
### Rolling Back Unsuccessful Upgrades
In the event that your Rancher Server does not upgrade successfully, you can rollback to your installation prior to upgrade:
- [Rollbacks]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks)
### Migrating from Rancher 1.6.x
content/rancher/v2.x/en/backups/rollbacks/_index.md → content/rancher/v2.x/en/upgrades/rollbacks/_index.md
+2 -2
View File
@@ -6,5 +6,5 @@ weight: 1010
If you upgrade your Rancher Server and the upgrade is unsuccessful, you can use the backup you created during the upgrade process to restore the previous version of Rancher, along with its data.
- [Rolling Back—Single Node Installs](./single-node-rollbacks/)
- [Rolling Back—High Availablity Installs](./ha-server-rollbacks/)
- [Rolling Back—Single Node Installs](({{< baseurl >}}/rancher/v2.x/en/rollbacks/single-node-rollbacks)
- [Rolling Back—High Availability Installs]({{< baseurl >}}/rancher/v2.x/en/rollbacks/ha-server-rollbacks)
content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md → content/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/_index.md
+4 -5
View File
@@ -2,7 +2,7 @@
title: Rolling Back—High Availability Installs
weight: 50
aliases:
- /rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/
- /rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks
---
If you upgrade Rancher, but the upgrade does not complete successfully, you may need to roll back your Rancher Server to its last healthy state before upgrade. To restore Rancher:
@@ -57,14 +57,13 @@ kubectl --kubeconfig=kube_config_rancher-cluster.yml set image deployment/cattle
## Troubleshooting
With _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:
With **RKE 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.
@@ -75,5 +74,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 **RKE 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.
content/rancher/v2.x/en/backups/rollbacks/single-node-rollbacks/_index.md → content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
+2
View File
@@ -1,6 +1,8 @@
---
title: Rolling Back—Single Node Installs
weight: 25
aliases:
- /rancher/v2.x/en/backups/rollbacks/single-node-rollbacks
---
Rolling back an unsuccessful Rancher upgrade requires you to
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.