In the VSP One SDS Block and SDS Cloud System Administration and VSP One SDS Cloud for Azure Setup and Configuration, you perform deployment when configuring Microsoft Azure environment and VSP One SDS Block storage clusters.
If an error occurs during deployment, take action according to the following flow.
If deployment results in an error, you can identify the error cause by confirming the deployment status and error details.
You can see the the Troubleshooting Guide for Microsoft Azure by visiting the following website.
|
What happens |
Cause |
Action to be taken |
|---|---|---|
|
An error indicating no ARM template file exists occurs. |
No ARM template file exists. |
See Managing configuration files (Cloud for Microsoft Azure) in the VSP One SDS Block and SDS Cloud System Administration to verify that the VM configuration file necessary for deployment exists on the working folder, and then reperform deployment. |
|
Execution results in an error. |
Input parameters violate the Microsoft Azure specifications or no items are input. |
Enter the correct values for the input parameters, and then reperform deployment. |
|
Users are not granted necessary privileges (Privileges necessary for creating resources are not granted to users.). |
Grant the necessary privileges as described in User privileges in the VSP One SDS Cloud for Azure Setup and Configuration. |
|
|
You are using a region that does not meet the setup prerequisites. |
Refer to Verify Setup Prerequisites in the and ensure that the prerequisites for building VSP One SDS Block are met. If the conditions are not met, review your environment. |
|
|
Azure quotas (resource creation upper limit) are violated. |
See the Microsoft Azure user guide to review the upper limit quota. |
|
|
The resource name generated from the parameter value is duplicated (already exists). |
Correct the parameter value to resolve the resource name duplication, and then reperform deployment. Also, verify that no resource created during the past deployment remains. |
|
|
Network creation and settings have errors. |
See Configuring a Microsoft Azure environment in the VSP One SDS Cloud for Azure Setup and Configuration to review the settings. |
|
|
The role you attempted to create already exists. (The error code displayed was "RoleDefinitionWithSameNameExists" or "RoleAssignmentUpdateNotPermitted".) |
Refer to Actions to be taken for errors occurring during role creation (Cloud for Microsoft Azure), delete the role, and then redeploy. |
|
|
The storage account you tried to create already exists. (The error code displayed was "StorageAccountInAnotherResourceGroup" or "StorageAccountAlreadyTaken".) |
Modify the storage account name (storageAccountName parameter) to ensure resource names are unique, then redeploy. Also verify that no storage accounts created by previous deployments remain. |
|
|
A temporary error occurs or an operation conflict occurs on the cloud side. |
Reperform deployment. |
|
|
Cloud Shell was disconnected. |
Cloud Shell verification timed out. |
Connect to Cloud Shell again, and then reperform deployment. If the window cannot be displayed after retrying connection to Cloud Shell, verify that connection with Microsoft Azure is normal, and then reperform deployment. |
If deployment results in failure at the time of initial installation of a storage cluster, any resources created during the process remain. Therefore, you need to delete those remaining resources before recreating resources. Delete remaining resources, and then reperform deployment.
For details about how to delete resources, see Deleting storage clusters (Cloud for Microsoft Azure) in the VSP One SDS Block and SDS Cloud System Administration.