You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we try to create a dynamodb table on a region where the maximum number of tables has been reached, terraform retries the table creation until it times outs and display an error without giving any clue on the issue (it shows in debug)
Example error:
terraform apply
aws_dynamodb_table.example: Creating...
arn: "" => "<computed>"
attribute.#: "" => "1"
attribute.4228504427.name: "" => "id"
attribute.4228504427.type: "" => "S"
hash_key: "" => "id"
name: "" => "example"
read_capacity: "" => "5"
stream_arn: "" => "<computed>"
stream_enabled: "" => "<computed>"
stream_view_type: "" => "<computed>"
write_capacity: "" => "5"
aws_dynamodb_table.example: Still creating... (10s elapsed)
aws_dynamodb_table.example: Still creating... (20s elapsed)
aws_dynamodb_table.example: Still creating... (30s elapsed)
[...]
aws_dynamodb_table.example: Still creating... (9m0s elapsed)
aws_dynamodb_table.example: Still creating... (9m10s elapsed)
aws_dynamodb_table.example: Still creating... (9m20s elapsed)
aws_dynamodb_table.example: Still creating... (9m30s elapsed)
Error applying plan:
1 error(s) occurred:
* aws_dynamodb_table.example: Unable to create DynamoDB table 'example' after 6 attempts
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Hey @lbernail, thanks for the issue! I believe this is an issue within the aws-sdk, where the Request isn't correctly returning the 400 response from the API. Opened the upstream issue to track a possible solution: aws/aws-sdk-go#1271
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 12, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When we try to create a dynamodb table on a region where the maximum number of tables has been reached, terraform retries the table creation until it times outs and display an error without giving any clue on the issue (it shows in debug)
Example error:
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
The issue:
Panic Output
None
Expected Behavior
Terraform should catch the issue (instead of retrying until timeout) and display the AWS error
Actual Behavior
Terraform keeps retrying until timeout. When reaching timeout it does give any info on the AWS error
Steps to Reproduce
terraform apply
References
I did not find any
The text was updated successfully, but these errors were encountered: