starlingx/docs
Code Issues Proposed changes
2b2cc0b045
docs/doc/source/dist_cloud/kubernetes/failure-prior-to-the-installation-of-n-plus-1-load-on-a-subcloud.rst
Ron Stone 39e3de7291 Fix variable markup (r6,r7,r8,dsR7,dsR8) 
Documentation imported from XML incorrectly wrapped variable names in double
braces such as <<varname>>, instead of <varname>. This review corrects these
instances.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I70cb7e4030a92b3bc83c7b01a6f4135f9cb0e5ad
2023-03-14 14:34:44 +00: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