Uma introdução ao Cloud Composer 3 avaliações

dag ends with errors, because i dont have roles/composer.ServiceAgentV2Ext permissions, i lost 1 hour waiting

Patricio D. · Revisado há almost 2 years

BharathKumar R. · Revisado há almost 2 years

Does not work. It will not allow me to create the composer environment.

Liang M. · Revisado há almost 2 years

Sridhar B. · Revisado há almost 2 years

the environment failed to be created. already two times.....

Grégory L. · Revisado há almost 2 years

Does not work. It will not allow me to create the composer environment.

Liang M. · Revisado há almost 2 years

Grégory L. · Revisado há almost 2 years

Jim T. · Revisado há almost 2 years

Cloud composer took 47 minutes to create and had errors. I did not have time left in the lab to try again.

Evan K. · Revisado há almost 2 years

I followed the steps, and the Composer Environment is not being created. The lab finished automatically while I was waiting for the Composer Environment to be created, and I got a message saying that I was not following the lab's guidelines and my account could be suspended if I continue with that behaviour.

Jesús P. · Revisado há almost 2 years

It didn't work properly and timed everybody out to begin with. After restarting some of the steps didn't seem to make sense.

Orry D. · Revisado há almost 2 years

Zeev S. · Revisado há almost 2 years

Sundara Tejaswi D. · Revisado há almost 2 years

Stephen C. · Revisado há almost 2 years

instructions are not correctly given for this Lab. I assume some Role permissions are missing like "Cloud Composer API Service Agent". or GKE services might be busy. have tried number of times. I am not happy with this Lab.

Anil S. · Revisado há almost 2 years

Ankit P. · Revisado há almost 2 years

instructions are not correctly given for this Lab. I assume some Role permissions are missing like "Cloud Composer API Service Agent".

Anil S. · Revisado há almost 2 years

CREATE operation on this environment failed 1 minute ago with the following error message: Some of the GKE pods failed to become healthy. Please check the GKE logs for details, and retry the operation. The issue may be caused by missing IAM roles in the following Service Accounts: - service-731342471549@cloudcomposer-accounts.iam.gserviceaccount.com in project 731342471549 is missing role roles/composer.ServiceAgentV2Ext The list of missing roles is generated without checking individual permissions in IAM custom roles. If any of the Service Accounts above uses custom IAM roles, its permissions may be sufficient and a corresponding warning may be ignored.

zharina francis f. · Revisado há almost 2 years

Liang M. · Revisado há almost 2 years

not responsive

Anil S. · Revisado há almost 2 years

not responsive

Anil S. · Revisado há almost 2 years

Piotr L. · Revisado há almost 2 years

Minal G. · Revisado há almost 2 years

komal A. · Revisado há almost 2 years

Juan Carlos M. · Revisado há almost 2 years