Incident - Cloud Composer - Global

[Steve]

Hi everyone, 

I saw in the google service health cloud status

we are having an incident

it is said that there is a Workaround: 

Customers can retry creation or create newer Composer version (>=2.1)

but, I have tried to create airflow version >=2.1 using these commands :

gcloud composer environments create demo-environment \
  --location us-central1 \
  --image-version composer-2.2.0-airflow-2.5.1
in the Cloud Composer console, it is spinning all the time (40 minutes to 1 hour)

I have changed the image version into :

composer-2.1.15-airflow-2.5.1

composer-2.1.14-airflow-2.3.4

composer-2.1.13-airflow-2.4.3
composer-2.1.12-airflow-2.3.4
composer-2.1.9-airflow-2.4.3
composer-2.1.1-airflow-2.3.4

but nothing works, I have waited 40 minutes - 1 hour hoping it will be created, 

but it got an error timeout, is there anyone who succeeded in creating airflow using CLI?

I have tried to create Cloud Composer using Cloud Console but it can't be created because of a service account issue.

Best regards

Steve

[Steve]

Hi everyone, I got it working by,

adding the policy-binding using CLI to the service account after I grant the composer service account when creating the environment,

and I can confirm that the Environment is created correctly,

Hope this helps

Best regards

Steve