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 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.

Before upgrading controller-0

  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.

  2. Complete the upgrade.

    $ 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 StarlingX Simplex software via network or USB manually.

  2. Verify and configure IP connectivity. External connectivity is required to run the Ansible restore playbook. The StarlingX 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 ip addr command. Otherwise, manually configure an IP address and default IP route.

    Note

    If there are patches on the AIO-SX system prior to the upgrade, Ansible restore playbook will install the patches and cause a reboot of the system. The reboot will lead to the loss of IP connectivity configuration. Verify and re-configure IP connectivity and re-run the Ansible restore playbook to complete the platform restore.

  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.

    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

    $ system host-unlock controller-0

  5. 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.

  6. Complete the upgrade.

    $ system upgrade-complete