starlingx/docs
Code Issues Proposed changes
Files
c78318accfc3265bd261fcd89a25e21f8449784c
docs/doc/source/updates/kubernetes/aborting-simplex-system-upgrades.rst
Ron Stone dd8efe5f85 Upgrades edits (r6,r7,dsR6,dsR7) 
Copy edits for typos, markup and other technical issues.
Fix case typo
Fix merge conflicts.
Resolve FixMe issues.
Minor copy edit updates.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I7d710d3faa957c1cb66cc18c9a248a567e7c580f
2022-10-27 06:34:33 -04:00

3.3 KiB
Raw Blame History

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 upgrade-complete command is issued. Once this command is issued the upgrade can not be aborted. If you must return to the previous release, 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.

Before upgrading controller-0

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

    ~(keystone_admin)$ system upgrade-abort

    The upgrade state is set to aborting. Once this is executed, it cannot be cancelled; the upgrade must be completely aborted.

  2. Complete the upgrade.

    ~(keystone_admin)$ 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.

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.

  1. Install the previous release of Simplex software via network or USB.

  2. Verify and configure IP connectivity. External connectivity is required to run the Ansible restore playbook. The boot image will out all interfaces so the server may have obtained an IP address and have external IP connectivity if a server is present in your environment. Verify this using the ip addr command. Otherwise, manually configure an IP address and default IP route.

  3. Restore the system data. The restore is preserved in /opt/platform-backup.

    The system will be restored to the state when the upgrade-start command was issued. Follow the process in 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.

  4. Unlock controller-0

    ~(keystone_admin)$ system host-unlock controller-0

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

    ~(keystone_admin)$ system upgrade-abort

    The upgrade state is set to aborting. Once this is executed, it cannot be cancelled; the upgrade must be completely aborted.

  6. Complete the upgrade.

    ~(keystone_admin)$ system upgrade-complete