From aecef1306ed5c40ab9bf82966e2782413a59d382 Mon Sep 17 00:00:00 2001 From: urgemerge Date: Wed, 15 Aug 2018 18:36:30 +0200 Subject: [PATCH] changing the order of checking after upgrade changing the documented order of checking if an upgrade has succeeded --- .../rancher/v2.x/en/upgrades/single-node-upgrade/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md index f0631f3b1b6..f2e7dafd952 100644 --- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md @@ -58,12 +58,12 @@ docker run -d --volumes-from rancher-data --restart=unless-stopped \ >
>**Note:** After upgrading Rancher Server, data from your upgraded server is now saved to the `rancher-data` container for use in future upgrades. +1. Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window. + 1. Remove the previous Rancher Server container. If you only stop the previous Rancher Server container (and don't remove it), the container may restart after the next server reboot. -1. Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window. - **Result:** Rancher Server is upgraded to the latest version. >**Note:** If your upgrade does not complete successfully, you can roll Rancher Server and its data back to its last healthy state. For more information, see [Restoring Backups—Single Node Installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/single-node-restoration/).