starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/failure-prior-to-the-installation-of-n+1-load-on-a-subcloud.rst
Adil ac4d8fea44 Node Management and Distributed cloud Guide updates 
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
2021-05-27 16:31:17 -03:00

1.5 KiB
Raw Blame History

Failure Prior to the Installation of N+1 Load on a Subcloud

You may encounter some errors prior to Installation 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 any one of the following:

  • Insufficient disk space on scratch filesystems
  • Missing subcloud install values
  • Invalid license
  • Invalid/corrupted load file
  • The /home/sysadmin directory on the subcloud is too large

If you encounter any of the above errors, follow this procedure to retry the orchestrated upgrade after addressing the cause of failure:

  1. Delete the failed upgrade strategy

    ~(keystone_admin)]$  dcmanager upgrade-strategy delete

  2. Create a new upgrade strategy.

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

    Note

    If only one subcloud fails the upgrade, specify the name of the subcloud in the command.

  3. Apply the new upgrade strategy.

    ~(keystone_admin)]$ dcmanager upgrade-strategy apply

  4. Verify the upgrade strategy status

    ~(keystone_admin)]$ dcmanager strategy-step list