-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Project tainted #18455
Comments
@alfonsozamorac Thanks for filing the ticket. Yes, that's known issue and it should be fixed by GoogleCloudPlatform/magic-modules#10046 which is released v5.19.0. Would mind upgrading to a 5.19.0+ version and see if this issue still occurs |
Thank you very much for the response @shuyama1. We will try to upgrade the version to see if it solves the problem. For projects that have a 'tainted' state, what would be the solution? Should we untaint the resource using |
Upgrading the version wouldn't resolve the issue for existing resources, unless you let Terraform delete and recreate them. Given the fact that you cannot destroy and create the projects because the policy prevents recreation for 30 days, I think you can run |
I executed |
Great! Glad it worked. Closing this issue now. Feel free to reopen or file a new one if the issue happens again. Thanks! |
Community Note
Terraform Version & Provider Version(s)
Terraform v1.2.9
provider registry.terraform.io/hashicorp/google v5.10.0
provider registry.terraform.io/hashicorp/google-beta v5.10.0
Affected Resource(s)
google_project
Terraform Configuration
Debug Output
Expected Behavior
Successful project creation
Actual Behavior
It fails because the Compute Engine API is not enabled and cannot delete default networks because I have the variable
auto_create_network = false
. When you try to do a second apply the project appears in 'tainted' state and needs to be destroyed and recreated. It doesn't always happen, making it difficult to reproduce the error.Steps to reproduce
terraform apply
terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: