starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/failure-during-the-installation-or-data-migration-of-n+1-load-on-a-subcloud.rst
Adil cfa6850d84 Distributed Cloud Upgrades 
Added new content to DC guide

List of impacted topics:

       -Upgrade Management Overview
       -Upgrading the SystemController Using the CLI
       -Distributed Upgrade Orchestration Process Using the CLI
       -Robust Error Handling During An Orchestrated Upgrade
       -Failure Prior to the installation of N+1 Load on a Subcloud
       -Failure During the Installation or Data Migration of N+1 Load on a Subcloud
          - Removed section-> Failure Caused by Invalid Docker Registry Certificate


Story: TBD
Task: TBD


Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I8538dd6bda8651d76964f64c250df627bace75cb
2021-06-04 13:14:35 +00:00

2.9 KiB
Raw Blame History

Failure During the Installation or Data Migration of N+1 Load on a Subcloud

You may encounter some errors during Installation or Data migration of the N+1 load on a subcloud. This section explains the errors and the steps required to fix these errors.

Errors can occur due to one of the following:

  • One or more invalid install values
  • A network error that results in the subcloud being temporarily unreachable

Failure Caused by Install Values

If the subcloud install values contain an incorrect value, use the following command to fix it.

~(keystone_admin)]$ dcmanager subcloud update <<subcloud-name>> --install-values <<subcloud-install-values-yaml>>

This type of failure is recoverable and you can retry the orchestrated upgrade for each of the failed subclouds using the following procedure:

  1. Delete the failed upgrade strategy.

    ~(keystone_admin)]$ dcmanager upgrade-strategy delete

  2. Create a new upgrade strategy for the failed subcloud.

    ~(keystone_admin)]$ dcmanager upgrade-strategy create <<subcloud-name>> --force <<additional options>>

    Note

    If the upgrade failed during the -SX upgrade or data migration, the subcloud availability status is displayed as 'offline'. Use the --force option when creating the new strategy.

  3. Apply the new upgrade strategy.

    ~(keystone_admin)]$ dcmanager upgrade-strategy apply

  4. Verify the upgrade strategy status.

    ~(keystone_admin)]$ dcmanager strategy-step list

Failure Post Data Migration on a Subcloud

Once the data migration on the subcloud is completed, the upgrade is activated and finalized. If failure occurs:

  • Check specified log files
  • Follow the recovery procedure. See Failure Prior to the Installation of N+1 Load on a Subcloud <failure-prior-to-the-installation-of-n+1-load-on-a-subcloud>

partner