starlingx/docs
Code Issues Proposed changes
docs/doc/source/updates/kubernetes/rolling-back-a-software-upgrade-before-the-second-controller-upgrade.rst
Ron Stone 0012d76f09 Add updates and upgrades content 
Some substitutions also added to accomodate StX vs partner file naming.
Add 750.006 alarm to performing-an-orchestrated-upgrade

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I33588f3c1b22cd0dbc96133cf8eb056c8c2e5162
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-05-17 07:12:27 -04:00

1.9 KiB
Raw Blame History

Roll Back a Software Upgrade Before the Second Controller Upgrade

You can perform an in-service abort of an upgrade before the second Controller (controller-0 in the examples of this procedure) have been upgraded.

  1. Abort the upgrade with the upgrade-abort command.

    $ system upgrade-abort

    The upgrade state is set to aborting. Once this is executed, there is no canceling; the upgrade must be completely aborted.

    The following states apply when you execute this command.

    • aborting:
      • State entered when system upgrade-abort is executed before upgrading controller-0.
      • Remain in this state until the abort is completed.

  2. Make controller-0 active.

    $ system host-swact controller-1

    If controller-1 was active with the new upgrade release, swacting back to controller-0 will switch back to using the previous release databases, which were frozen at the time of the swact to controller-1. Any changes to the system that were made while controller-1 was active will be lost.

  3. Lock and downgrade controller-1.

    $ system host-lock controller-1
$ system host-downgrade controller-1

    The host is re-installed with the previous release load.

  4. Unlock controller-1.

    $ system host-unlock controller-1

  5. Complete the upgrade.

    $ system upgrade-complete

  6. Delete the newer upgrade release that has been aborted.

    $ system load-delete <loadID>