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

Proper error message for HTTP 409 while provisioning Google Cloud SQL instance #20972

Closed
gtirloni opened this issue Apr 9, 2019 · 3 comments
Closed

Comments

@gtirloni
Copy link

gtirloni commented Apr 9, 2019

The issue is described in detail in #4557:

* google_sql_database_instance.default: Error, failed to create instance master-instance: googleapi: Error 409: The instance or operation is not in an appropriate state to handle the request., invalidState

This happens because instance names cannot be reused for up to a week after it's deleted.

The enhancement landed in #4577 but it's not showing properly which is leading to confused users.

Terraform 0.11.13

@apparentlymart
Copy link
Contributor

Hi @gtirloni! Sorry for this unhelpful error message.

It looks like this message comes from inside the Google Cloud Platform provider code, rather than from the Terraform Core code. Back in 2016 when #4577 was merged, all of the providers were inside this codebase too, but they've since been split out into their own repositories.

I'm going to ask our bot to migrate this over to the Google Cloud Platform provider repository so that the provider team can see it and decide what to do about it.

Thanks for reporting this!

@ghost
Copy link

ghost commented Apr 10, 2019

This issue has been automatically migrated to hashicorp/terraform-provider-google#3404 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-google#3404.

@ghost
Copy link

ghost commented Aug 13, 2019

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 ghost locked and limited conversation to collaborators Aug 13, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants