ac4d8fea44
Global Pass Upgrades
Added content from emails attached to ticket and sharepoint
Pacth 01: inputs from email by Greg
Patch 03: Created new section for subcloud group
updated table 1 shared system configurations
Patch 04: corrected typos (Mary's comments)
Patch 05: solved merged conflict
patch 06: removed broken link
Story: TBD
Task: TBD
Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I60b0a40a60a44d30429cd3a4dd8374c16345951a
1.8 KiB
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:
- Allow the failed strategy to complete on its own.
- Check the output using the
dcmanager strategy-step listcommand for failures, if any. - 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>. - 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>