Open fsequeira1 opened 3 years ago
Is this consistently reproducible? Unfortunately I don't see an easy fix for this if it's a race condition.
@morgante It's not 100% consistent, but it's frequent
One possible fix would be to split node pools into two different resources: one for linux node pools and one for Windows node pools, with the latter dependent on the former. This would be a breaking change though.
For the record we are getting this exact problem.
We are still facing this problem. Is there any news regarding a timeline to solve this?
It's still on our backlog, but don't have a timeline.
If someone wants to pick it up in the meantime, I'd be happy to review a pull request.
I'm also getting this same problem but runs fine after second time.
Hi,
We are getting an error when trying to create a GKE cluster with a windows node pool. This is the error message:
Although this error happens, if we run the module a second time it runs perfectly without any error.
From the output and the tests performed this appears to be a timeout issue because the Linux node pool creation was completed
module.gke.google_container_node_pool.pools["node-pool"]: Creation complete after 6m45s
but the new windows node pool started immediately after and probably the Linux node wasn't ready yet.Side notes:
depends_on = [module.gke]
.Is there any other possible solution we are missing?
Used configuration:
@Edelf