starlingx/docs
Code Issues Proposed changes
Files
94e7cd3f2188956c1cfa31a7484032c46ce44c20
docs/doc/source/dist_cloud/kubernetes/robust-error-handling-during-an-orchestrated-upgrade.rst
Ron Stone 63d357562e Constrain label char set (r6,r5) 
Some characters in rST labels are not handled correctly by XSLT
post-processors.
This change fixes two known instances and modifies the newfile
tox job to handle these chars.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I535362dc40de6796b795b2ac86ef46a1edec685c
(cherry picked from commit cbc5d16a11)
2022-04-06 11:09:46 +00:00

1.6 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-plus-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-plus-1-load-on-a-subcloud
  • failure-during-the-installation-or-data-migration-of-n-plus-1-load-on-a-subcloud