starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/robust-error-handling-during-an-orchestrated-upgrade.rst
Ron Stone 10805c3e8f Apply dir convention to DC 
Moved all DC content under a kubernetes directory. This is needed
to allow title versioning distinctions in partner builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia7ab4fccc7cb9ed6c242cf584f237165f00e5ef2
2021-08-03 07:57:24 -04:00

1.8 KiB
Raw Blame History

Error Handling During An Orchestrated Upgrade

This section describes the errors you may encounter during an orchestrated upgrade and the steps you can use to troubleshoot the errors.

For a successful orchestrated upgrade, ensure the upgrade prerequisites, procedure, and postrequisites are met.

If a failure occurs, use the following general steps:

  1. Allow the failed strategy to complete on its own.
  2. Check the output using the dcmanager strategy-step list command for failures, if any.
  3. Address the cause of the failure. For more information, see Failure During the Installation or Data Migration of N+1 Load on a Subcloud <failure-during-the-installation-or-data-migration-of-n+1-load-on-a-subcloud>.
  4. Retry the orchestrated upgrade. For more information, see Distributed Upgrade Orchestration Process Using the CLI <distributed-upgrade-orchestration-process-using-the-cli>.

Note

Orchestrated upgrade can be retried for a group of failed subclouds that are still online using the upgrade-strategy create --group <group-id> command. Failed subclouds that are offline must be retried one at a time.

Failure Prior to the Installation of N+1 Load on a Subcloud <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 <failure-during-the-installation-or-data-migration-of-n+1-load-on-a-subcloud>