Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression - HTTP 409 while provisioning Google Cloud SQL instance - using a previously used db name #5179

Closed
javapapo opened this issue Dec 16, 2019 · 3 comments
Assignees
Labels

Comments

@javapapo
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

0.12.18

Affected Resource(s)

  • google_sql_database_instance

Terraform Configuration Files

Usual example from the documentation

Panic Output

Error: Error, failed to create instance xxxx: googleapi: Error 409: The instance or operation is not in an appropriate state to handle the request., invalidState

  on main.tf line 18, in resource "google_sql_database_instance" "instance":
  18: resource "google_sql_database_instance" "instance" {

Expected Behavior

Create the Cloud SQL instance

Actual Behavior

Timeout after 20m

Steps to Reproduce

  1. create a Cloud SQL instance with name db-1 using the console or terraform
  2. Delete the above instance
  3. Try to create a new tf stack using the same name db-1

Terraform will timeout after 20m

  1. Update your stack ..and specifically the name to something random db-1244553
  2. Re-Run the stack the DB will be created

References

@ghost ghost added the bug label Dec 16, 2019
@javapapo javapapo changed the title Regression - HTTP 409 while provisioning Google Cloud SQL instance - using a previously use name Regression - HTTP 409 while provisioning Google Cloud SQL instance - using a previously used db name Dec 16, 2019
@venkykuberan venkykuberan self-assigned this Dec 16, 2019
@venkykuberan
Copy link
Contributor

@javapapo You can't reuse the same instance name for up to a week. Please refer this issue #5101. Closing this one.

@javapapo
Copy link
Author

Ooh understood. thanks

@ghost
Copy link

ghost commented Mar 28, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants