4aef0abb31
Updated topic 'Abort Simplex System Upgrades' as detailed in jira Updated topics from distributed and updates guides -information from doc provided by David https://review.opendev.org/c/starlingx/docs/+/794309 Signed-off-by: Adil <mohamed.adilassakkali@windriver.com> Change-Id: Id47e93f1c57e579dca483e8d073902f933ef78bf
102 lines
3.2 KiB
ReStructuredText
102 lines
3.2 KiB
ReStructuredText
|
|
.. syj1592947192958
|
|
.. _aborting-simplex-system-upgrades:
|
|
|
|
=============================
|
|
Abort Simplex System Upgrades
|
|
=============================
|
|
|
|
You can abort a Simplex System upgrade before or after upgrading controller-0.
|
|
The upgrade abort procedure can only be applied before the
|
|
:command:`upgrade-complete` command is issued. Once this command is issued the
|
|
upgrade can not be aborted. If the return to the previous release is required,
|
|
then restore the system using the backup data taken prior to the upgrade.
|
|
|
|
Before starting, verify the upgrade data under `/opt/platform-backup`. This data
|
|
must be present to perform the abort process.
|
|
|
|
.. _aborting-simplex-system-upgrades-section-N10025-N1001B-N10001:
|
|
|
|
.. contents:: |minitoc|
|
|
:local:
|
|
:depth: 1
|
|
|
|
-----------------------------
|
|
Before upgrading controller-0
|
|
-----------------------------
|
|
|
|
.. _aborting-simplex-system-upgrades-ol-nlw-zbp-xdb:
|
|
|
|
#. Abort the upgrade with the upgrade-abort command.
|
|
|
|
.. code-block:: none
|
|
|
|
$ system upgrade-abort
|
|
|
|
The upgrade state is set to aborting. Once this is executed, there is no
|
|
canceling; the upgrade must be completely aborted.
|
|
|
|
#. Complete the upgrade.
|
|
|
|
.. code-block:: none
|
|
|
|
$ system upgrade-complete
|
|
|
|
At this time any upgrade data generated as part of the upgrade-start
|
|
command will be deleted. This includes the upgrade data in
|
|
/opt/platform-backup.
|
|
|
|
.. _aborting-simplex-system-upgrades-section-N10063-N1001B-N10001:
|
|
|
|
----------------------------
|
|
After upgrading controller-0
|
|
----------------------------
|
|
|
|
After controller-0 has been upgraded it is possible to roll back the software
|
|
upgrade. This involves performing a system restore with the previous release.
|
|
|
|
.. _aborting-simplex-system-upgrades-ol-jmw-kcp-xdb:
|
|
|
|
#. Install the previous release of |prod-long| Simplex software via network or
|
|
USB.
|
|
|
|
#. Verify and configure IP connectivity. External connectivity is required to
|
|
run the Ansible restore playbook. The |prod-long| boot image will DHCP out all
|
|
interfaces so the server may have obtained an IP address and have external IP
|
|
connectivity if a DHCP server is present in your environment. Verify this using
|
|
the :command:`ip addr` command. Otherwise, manually configure an IP address and default IP
|
|
route.
|
|
|
|
#. Restore the system data. The restore is preserved in /opt/platform-backup.
|
|
|
|
The system will be restored to the state when the :command:`upgrade-start`
|
|
command was issued. Follow the process in :ref:`Run Restore Playbook Locally on the
|
|
Controller <running-restore-playbook-locally-on-the-controller>`.
|
|
|
|
Specify the upgrade data filename as `backup_filename` and the `initial_backup_dir`
|
|
as `/opt/platform-backup`.
|
|
|
|
The user images will also need to be restored as described in the Postrequisites section.
|
|
|
|
#. Unlock controller-0
|
|
|
|
.. code-block:: none
|
|
|
|
$ system host-unlock controller-0
|
|
|
|
|
|
#. Abort the upgrade with the :command:`upgrade-abort` command.
|
|
|
|
.. code-block:: none
|
|
|
|
$ system upgrade-abort
|
|
|
|
The upgrade state is set to aborting. Once this is executed, there is no
|
|
canceling; the upgrade must be completely aborted.
|
|
|
|
#. Complete the upgrade.
|
|
|
|
.. code-block:: none
|
|
|
|
$ system upgrade-complete
|