starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/failure-prior-to-the-installation-of-n-plus-1-load-on-a-subcloud.rst
Ron Stone cbc5d16a11 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
2022-03-14 08:01:49 -04: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