From ba78f1e6827c41fcf744f00f69211a300846d44a Mon Sep 17 00:00:00 2001 From: Keane Lim Date: Tue, 21 Sep 2021 12:22:48 -0400 Subject: [PATCH] Clarify upgrade procedure to prevent lack of free space Change-Id: I0ae9b3e79e7648f36fdb811daa314464466ecf10 Signed-off-by: Keane Lim --- .../kubernetes/manual-upgrade-overview.rst | 15 +++++++++++---- .../upgrading-all-in-one-duplex-or-standard.rst | 4 ++-- .../kubernetes/upgrading-all-in-one-simplex.rst | 13 ++++++++++--- 3 files changed, 23 insertions(+), 9 deletions(-) diff --git a/doc/source/updates/kubernetes/manual-upgrade-overview.rst b/doc/source/updates/kubernetes/manual-upgrade-overview.rst index 13188dec6..6159d5e6c 100644 --- a/doc/source/updates/kubernetes/manual-upgrade-overview.rst +++ b/doc/source/updates/kubernetes/manual-upgrade-overview.rst @@ -23,10 +23,17 @@ This section describes the manual upgrade procedures. procedure, see |distcloud-doc|: :ref:`Orchestration Upgrade Overview `. -Before starting the upgrades process, the system must be “patch current,” there -must be no management-affecting alarms present on the system, the new software -load must be imported, and a valid license file for the upgrade must be -installed. +Before starting the upgrade process, ensure that the following conditions are +met: + +- The system is patch current. + +- There are no management-affecting alarms and the "system + health-query-upgrade" check passes. + +- The new software load has been imported. + +- A valid license file has been installed. The upgrade procedure is different for the All-in-One Simplex configuration versus the All-in-One Duplex, and Standard configurations. For more diff --git a/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst b/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst index ef495a517..c3ce7e49d 100644 --- a/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst +++ b/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst @@ -21,8 +21,8 @@ of |prod| software. restore operations, blade replacement, or upgrades. - The system must be "patch current". All updates available for the current - release running on the system must be applied. To find and download - applicable updates, visit the |dnload-loc|. + release running on the system must be applied, and all patches must be + committed. To find and download applicable updates, visit the |dnload-loc|. - Transfer the new release software load to controller-0 \(or onto a USB stick\); controller-0 must be active. diff --git a/doc/source/updates/kubernetes/upgrading-all-in-one-simplex.rst b/doc/source/updates/kubernetes/upgrading-all-in-one-simplex.rst index 79f340b65..c17a1351e 100644 --- a/doc/source/updates/kubernetes/upgrading-all-in-one-simplex.rst +++ b/doc/source/updates/kubernetes/upgrading-all-in-one-simplex.rst @@ -21,9 +21,16 @@ software. an upgrade. Home directories are not preserved during backup or restore operations, blade replacement, or upgrades. -- The system must be 'patch current'. All upgrades available for the current - release running on the system must be applied. To find and download - applicable upgrades, visit |dnload-loc| site. +- Ensure that the following conditions are met: + + - The system is patch current. + + - There should be sufficient free space in /opt/platform-backup. Remove + any unused files if necessary. + + - The new software load has been imported. + + - A valid license file has been installed. - Transfer the new release software load to controller-0 \(or onto a USB stick\); controller-0 must be active.