-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Possible flaky CI with remove_default_node_pool = true #1227
Comments
Upstream provider issue hashicorp/terraform-provider-google#10366 |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Hello everyone, Saw this issue and wanted to share my input on this and ask for any suggestions if there is a way to resolve the error even temporarily. At the moment I am able to reproduce the 400 Error 7/10 times while provisioning a GKE cluster via Terraform with the option remove_default_node_pool = true. The Terraform module I am running creates 4 resources: google_compute_network Each time it errors out on google_container_cluster, around 6min into the resource creation. If I set remove_default_node_pool = false. the module completes every time since it takes just a bit under 6 min to create the cluster. I am sharing the last few lines of terraform apply debug output including the received error message: https://gist.githubusercontent.com/jacknif3/062dce1ae3d23e01d1295f5470e0091f/raw/264bf02ad59959ce50d081f116a1c36ed4028c51/gistfile1.txt Please let me know if you need to see how I'm creating the resources or anything else, I'll be glad to try anything to resolve this issue. Additional info: Terraform version: 1.3.4 |
TL;DR
Possible flaky CI with
remove_default_node_pool = true
Expected behavior
No response
Observed behavior
No response
Terraform Configuration
Terraform Version
Additional information
No response
The text was updated successfully, but these errors were encountered: