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/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:
Delete the failed upgrade strategy
~(keystone_admin)]$ dcmanager upgrade-strategy delete
Create a new upgrade strategy.
~(keystone_admin)]$ dcmanager upgrade-strategy create <additional options>
If only one subcloud fails the upgrade, specify the name of the subcloud in the command.
Apply the new upgrade strategy.
~(keystone_admin)]$ dcmanager upgrade-strategy apply
Verify the upgrade strategy status
~(keystone_admin)]$ dcmanager strategy-step list