Відгуки: Знайомство з Google Cloud: початок роботи з Cloud Marketplace

user access is broken. UX differs from text.

Andrew M. · Відгук надано 19 днів тому

Oscar L. · Відгук надано 19 днів тому

Terrible. Did not work

Jad B. · Відгук надано 19 днів тому

Krutika D. · Відгук надано 19 днів тому

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. · Відгук надано 19 днів тому

KM Abhi K. · Відгук надано 19 днів тому

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

Tadeo G. · Відгук надано 19 днів тому

lamp was not deploying

Lailani B. · Відгук надано 19 днів тому

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

Arthur E. · Відгук надано 19 днів тому

sandra e. · Відгук надано 19 днів тому

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

Mark C. · Відгук надано 19 днів тому

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. · Відгук надано 19 днів тому

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

Arthur E. · Відгук надано 19 днів тому

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

Andre L. · Відгук надано 19 днів тому

Bindu V. · Відгук надано 19 днів тому

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

Helen P. · Відгук надано 19 днів тому

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. · Відгук надано 19 днів тому

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

Tadeo G. · Відгук надано 19 днів тому

RISHIKA M. · Відгук надано 19 днів тому

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

Muzammal H. · Відгук надано 19 днів тому

Punith B. · Відгук надано 19 днів тому

Tadeo G. · Відгук надано 19 днів тому

not working very poor

AKASH V. · Відгук надано 19 днів тому

the app never finished installing. hung on last stage 3/3. the lab ran out of time. Tried again, followed the manual, same story - it never finishes Step 3/3 deploying

SERGII I. · Відгук надано 19 днів тому

Deploy blueprint: lamp-1 Just now qwiklabs-gcp-04-95cf8090fae2 Failed to perform tenant project creation

Rajeev S. · Відгук надано 19 днів тому