You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
current_status=$(gcloud container clusters list --project="$PROJECT" --filter=name:"$CLUSTER_NAME" --format="value(status)")
current_status="RUNNING RUNNING" instead of "RUNNING"
In this case the filter is returning multiple clusters instead of the cluster exactly named 'abc'
workaround:
Manually deleting cluster, firewall rules, and remote state. Passing skip_provisioners=true as per documentation and 413 to skip RUNNING check and wait for cluster RUNNING manually
The text was updated successfully, but these errors were encountered:
terraform -v
Terraform v0.13.5
gcloud -v
Google Cloud SDK 316.0.0
alpha 2020.10.23
beta 2020.10.23
bq 2.0.62
core 2020.10.23
gsutil 4.54
kubectl 1.15.11
environment
abc-xyz already exists and created successfully via terraform
abc is new cluster that is stuck in terraform apply
behaviour:
expected behaviour:
expected to return after cluster is in running status
replication:
In wait-for-cluster.sh
current_status="RUNNING RUNNING" instead of "RUNNING"
In this case the filter is returning multiple clusters instead of the cluster exactly named 'abc'
workaround:
Manually deleting cluster, firewall rules, and remote state. Passing
skip_provisioners=true
as per documentation and 413 to skip RUNNING check and wait for cluster RUNNING manuallyThe text was updated successfully, but these errors were encountered: