-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google-beta v3.10.0 fail to modify gke node pool status #5767
google-beta v3.10.0 fail to modify gke node pool status #5767
Comments
Currently trying to reproduce the error outside of the context of my project. Closing this issue in the meantime, as the elements in the current description are not enough to reproduce. |
I just hit this issue today when trying to upgrade a node pool for the first time with provider 3.11.0. It worked for me on 3.9.0. My error was the same as above. Looks like some undocumented change or regression in the code between 3.9 and 3.11 that creates the GKE API URL differently? This might be a related issue. |
Hi there,
We tried many versions of the provider: 3.2, 3.5, 3.9 and 3.12. |
Observed with 3.12.0 on a state created by a 2.x provider. Will try downgrades. |
Ah, got it- if it's happening for users upgrading from @davidxia: Thanks for the release range! And whoops, the change to node pools that landed in @sdif: I'd be surprised if I'm going to assign this to our bug onduty to fix the regression in |
Acknowledged, I see how to fix this. :) |
We ran into the same issue when trying to set |
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.12.20
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: