In the VSP One SDS Block and SDS Cloud System Administration and VSP One SDS Cloud for AWS Setup and Configuration, you use CloudFormation when configuring the AWS environment and a VSP One SDS Block storage cluster.
If an error occurs during CloudFormation execution, take action according to the flowchart shown further on in this section.
If CloudFormation execution results in an error, confirm events of CloudFormation and verify the items with an error status such as "CREATE_FAILED" from oldest to identify the error cause.
You can see the Troubleshooting Guide for AWS by visiting the following website.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#basic-ts-guide
|
Symptom |
Cause |
Action |
|---|---|---|
|
An error message indicating no CloudFormation template files exist is displayed. |
No CloudFormation template files exist. |
Review the location where CloudFormation files are stored, and then retry the operation. |
|
Execution results in an error. |
User input items violate the AWS specifications or no items are input when creating a stack. |
If stack creation is unsuccessful, all resources (including those whose creation was canceled) are deleted by the CloudFormation service. However, the stack itself, which was used in the deployment, remains. Delete the remaining stack before reperforming stack creation. The user must delete the abnormal stack (on the AWS Management Console), correct the error, and then reperform stack creation. |
|
IAM users are not assigned necessary privileges (policy necessary for creating resources is not assigned to IAM users). |
If stack creation is unsuccessful, all resources (including those whose creation was canceled) are deleted by the CloudFormation service. However, the stack itself, which was used in the deployment, remains. Delete the remaining stack before reperforming stack creation. The user must grant the necessary privileges to the IAM user as described in Overview in the VSP One SDS Cloud for AWS Setup and Configuration, and then reperform stack creation. |
|
|
The subnet IP address range specified when creating the stack was insufficient. |
If stack creation is unsuccessful, all resources (including those whose creation was canceled) are deleted by the CloudFormation service. However, the stack itself, which was used in the deployment, remains. Delete the remaining stack before reperforming stack creation. The user must verify the IP address range according to Overview in the VSP One SDS Cloud for AWS Setup and Configuration, and then reperform stack creation. |
|
|
AWS quotas (resource creation upper limit) are violated. |
If stack creation is unsuccessful, all resources (including those whose creation was canceled) are deleted by the CloudFormation service. However, the stack itself, which was used in the deployment, remains. Delete the remaining stack before reperforming stack creation. The user must delete the abnormal stack (on the AWS Management Console), take appropriate action according to quota information for each AWS service, and then reperform stack creation. |
|
|
The AWS capacity is insufficient. |
If stack creation was unsuccessful, you must delete the remaining stacks first. Users must delete the abnormal stacks (on the AWS Management Console), take appropriate action according to the AWS message, and then reperform stack creation. |
|
|
The CloudFormation console cannot be loaded. |
In some cases, the CloudFormation console cannot be loaded even when communication is normal. |
Reload the page and verify that the window opens normally. If a window is not successfully displayed after reloading, verify that communication with AWS is normal, and then retry the operation. |