-
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
Error: NodePool was created in the error state RUNNING_WITH_ERROR #10823
Comments
Not sure if it is related - I get a similar problem on asia-northeast1 and asia-northeast2, but asia-northeast3 the same code works fine. |
If you can capture debug logs with There's probably a space to improve the error message at least, provided the API provides a useful one. |
Can you check the node pool in the GCP console? I recently ran into this issue and the console gave more information about the error-- IP exhaustion in the secondary ip range. I was using /24 blocks for the secondary ip range (set by another terraform module or by console) and the cluster was being created with the default 110 pods per node. This article helped me out quite a bit with understanding how this exhaustion can happen. https://cloud.google.com/kubernetes-engine/docs/how-to/multi-pod-cidr I changed default pods per node to a modest 16 and voila. |
This helped to resolve the issue. Thanks |
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. |
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
1.1.2
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Error: NodePool cp-ofs-poc-gke-cluster-node was created in the error state "RUNNING_WITH_ERROR"
Expected Behavior
Node has to be created and status should be running.
Actual Behavior
Node created with error state "Running_With_Error"
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: