Google Cloud Fundamentals: Getting Started with Cloud Marketplace avis

DEPLOY IS NOT WORKING

Carlos Antonio D. · Examiné il y a 1 jour

Something is wrong with the tenant project

sandra e. · Examiné il y a 1 jour

sandra e. · Examiné il y a 1 jour

esta dando erro ao criar a lamp stack

Cássio M. · Examiné il y a 1 jour

user access is broken. UX differs from text.

Andrew M. · Examiné il y a 1 jour

Oscar L. · Examiné il y a 1 jour

Terrible. Did not work

Jad B. · Examiné il y a 1 jour

Krutika D. · Examiné il y a 1 jour

Fuck you and your stupid fucking lab. Fuck you onestly man. I'm already low on credits and your vague instructions are not fucking helping why do I have to go ask gemini wtf is going on only for it to tell me refresh the page it's a bug now i'm out of time and I have to waste more credits on this stupid fucking lab fuck you you greedy evil muthafuckers.

sicelo m. · Examiné il y a 1 jour

KM Abhi K. · Examiné il y a 1 jour

el lab no sirve, me marco el mismo error todas las veces que lo intente, si use modo incognito

Tadeo G. · Examiné il y a 1 jour

lamp was not deploying

Lailani B. · Examiné il y a 1 jour

Não consegui fazer o deploy. Dava erro de tenant

Arthur E. · Examiné il y a 1 jour

sandra e. · Examiné il y a 1 jour

LAMP stack would not deploy. Tenant creation failed. Again. Lab is broken.

Mark C. · Examiné il y a 1 jour

Voici un feedback concis que tu peux coller directement : Deployment consistently fails with "Failed to perform tenant project creation" (Infrastructure Manager) I attempted to deploy the LAMP Stack solution via Cloud Marketplace on two separate lab attempts (different projects/zones). Both times, the deployment blueprint "lamp-1" failed almost immediately with: Failed to perform tenant project creation Cloud Logging shows repeated IAM errors from service-agent-manager: Exception calling IAM: There were concurrent policy changes. Please retry the whole read-modify-write with exponential backoff. Exception calling IAM: Service account [ID] does not exist. This looks like a backend race condition where the service account isn't fully propagated in IAM before Infrastructure Manager tries to assign it permissions — not an error on my end (I followed the lab steps exactly, correct zone/machine type each time). Because of this, I burned through my lab time on both attempts and was unable to complete/validate the task, costing me approximately 10-15 credits with nothing to show for it. Please look into the tenant project creation flow for LAMP Stack deployments, and consider crediting back the failed attempts.

Isaac K. · Examiné il y a 1 jour

Não consegui fazer o deploy. Dava erro de tenant

Arthur E. · Examiné il y a 1 jour

Ocorreu um erro blueprint na criação. não foi possível concluir por isso.

Andre L. · Examiné il y a 1 jour

Bindu V. · Examiné il y a 1 jour

deploying the LAMP never got past the deploying screen so I couldn't test that it had worked

Helen P. · Examiné il y a 1 jour

It didn't get deployed. Error out with the below: Deploy blueprint: lamp-1 Just now qwiklabs-gcp-01-f5cd75ae5a1e Failed to perform tenant project creation

Sujoy G. · Examiné il y a 1 jour

el lab no sirve, me marco el mismo error todas las veces que lo intente, si use modo incognito

Tadeo G. · Examiné il y a 1 jour

RISHIKA M. · Examiné il y a 1 jour

I can't deploy the LAMP Stack. It keeps loading and does not deploy.

Muzammal H. · Examiné il y a 1 jour

Punith B. · Examiné il y a 1 jour