In the VSP One SDS Block and SDS Cloud System Administration and VSP One SDS Cloud for GCP Setup and Configuration, you use Terraform when configuring the Google Cloud environment and a VSP One SDS Block storage cluster.
If an error occurs during Terraform execution, take action according to the following flow.
If Terraform execution results in an error, you can identify the error cause by confirming the console output during Terraform execution and then confirming the displayed error status items from the top in the order.
You can see the Troubleshooting Guide for Google Cloud by visiting the following website.
-
Troubleshooting for deployment error
https://cloud.google.com/infrastructure-manager/docs/troubleshoot-deployments
|
What happens |
Cause |
Action to be taken |
|---|---|---|
|
The Terraform template file is in the "No configuration files" error status (existent error). |
No Terraform template file exists. |
See Managing configuration files (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration to verify that the VM configuration file necessary for Terraform execution exists on the working directory, and then resume the Terraform execution. |
|
Execution results in an error. |
User input items in the Terraform parameter violate the Google Cloud specifications or no items are input. |
Enter the correct setting value for the Terraform parameter, and then resume the Terraform execution. |
|
IAM users are not granted necessary privileges (Privileges necessary for creating resources are not granted to IAM users.). |
Grant the necessary privileges to the IAM user as described in Overview in the VSP One SDS Cloud for GCP 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. |
|
|
Google Cloud quotas (resource creation upper limit) are violated. |
See the Google Cloud user guide to review the upper limit quota. |
|
|
No buckets exist ("storage: bucket doesn't exist") or bucket specification is incorrect. |
Verify that the bucket specified in the backend.auto.tfvars file exists and the correct bucket is specified, and then resume the Terraform execution. |
|
|
The resource name generated from the parameter value is duplicated (already exists). |
Correct the duplicated Terraform parameter, and then resume the Terraform execution. |
|
|
Cloud Shell was disconnected. |
Cloud Shell verification timed out. |
Retry connection with Cloud Shell, and then resume application by using Terraform Plan. If the window cannot be displayed after retrying connection to Cloud Shell, verify that connection with Google Cloud is normal, and then resume the Terraform execution. |
If Terraform Apply 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 the remaining resources (as described in Deleting Storage Cluster (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration), and then run Terraform Apply again.