starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/robust-error-handling-during-an-orchestrated-upgrade.rst
Ngairangbam Mili a8c694aaab Subcloud Deployment/Orchestrated Upgrading Error Root Cause Analysis - PART 2 (ds8) 
Original master review: https://review.opendev.org/c/starlingx/docs/+/895870

Change-Id: I50d75dda42c09d56c7da50320667bd92028244f9
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
2023-10-18 15:43:42 +00: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-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.

partner

  • 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