ネットワーク ロードバランサを設定する のレビュー

Puga leslie · 約2ヶ月前にレビュー済み

RODRÍGUEZ MARTÍNEZ NICOLÁS IGNACIO · 約2ヶ月前にレビュー済み

김 도영 · 約2ヶ月前にレビュー済み

Jaramillo Nelson · 約2ヶ月前にレビュー済み

Jaramillo Nelson · 約2ヶ月前にレビュー済み

Amistoso Emman · 約2ヶ月前にレビュー済み

Jaworski Jarosław · 約2ヶ月前にレビュー済み

Terrible experience - it was impossible to create required instances within the specific zone. Other steps/tasks were accepted/accomplished, resulting in 70%. Credit wasted.

Janousek Pavel · 約2ヶ月前にレビュー済み

Unable to provision resources in us-central1. No zones avaiable

Fogle Kris · 約2ヶ月前にレビュー済み

It was not working

Arias Rodas Miguel Geovanny · 約2ヶ月前にレビュー済み

Entire us-central1 region was out of e2-small and e2-micro capacity

Ng Eng Kit Elvin · 約2ヶ月前にレビュー済み

ec2 pool was exhausted and I could not even finish first steps

Carnogursky Michal · 約2ヶ月前にレビュー済み

unable to create VM in the zone mentioned in lab due to availability issue

Samantaroy Arpita · 約2ヶ月前にレビュー済み

Aguilar Sanchez Jonathan · 約2ヶ月前にレビュー済み

All machine types I tried (8 tested) gave me a RESOURCE_POOL_EXHAUSTED error

Watson James · 約2ヶ月前にレビュー済み

Dominguez Jena · 約2ヶ月前にレビュー済み

P VIJAYPRASANNA · 約2ヶ月前にレビュー済み

borja jenelle · 約2ヶ月前にレビュー済み

karinda yoel charlye · 約2ヶ月前にレビュー済み

No resources available for this lab

Muinde Caleb · 約2ヶ月前にレビュー済み

Dominguez Jena · 約2ヶ月前にレビュー済み

Marani Giacomo · 約2ヶ月前にレビュー済み

Welcome to Cloud Shell! Type "help" to get started. Your Cloud Platform project in this session is set to qwiklabs-gcp-04-ac0ef6ae2d54. Use `gcloud config set project [PROJECT_ID]` to change to a different project. student_02_c01343d6ad20@cloudshell:~ (qwiklabs-gcp-04-ac0ef6ae2d54)$ gcloud auth list Credentialed Accounts ACTIVE: * ACCOUNT: student-02-c01343d6ad20@qwiklabs.net To set the active account, run: $ gcloud config set account `ACCOUNT` student_02_c01343d6ad20@cloudshell:~ (qwiklabs-gcp-04-ac0ef6ae2d54)$ gcloud config list project [core] project = qwiklabs-gcp-04-ac0ef6ae2d54 Your active configuration is: [cloudshell-12140] [environment: untagged] Read more to tag: g.co/cloud/project-env-tag. student_02_c01343d6ad20@cloudshell:~ (qwiklabs-gcp-04-ac0ef6ae2d54)$ gcloud config set compute/region us-central1 Updated property [compute/region]. student_02_c01343d6ad20@cloudshell:~ (qwiklabs-gcp-04-ac0ef6ae2d54)$ gcloud config set compute/zone us-central1-a Updated property [compute/zone]. student_02_c01343d6ad20@cloudshell:~ (qwiklabs-gcp-04-ac0ef6ae2d54)$ gcloud compute instances create www1 \ --zone=us-central1-a \ --tags=network-lb-tag \ --machine-type=e2-small \ --image-family=debian-12 \ --image-project=debian-cloud \ --metadata=startup-script='#!/bin/bash apt-get update apt-get install apache2 -y service apache2 restart echo " <h3>Servidor da web: www1</h3>" | tee /var/www/html/index.html' ERROR: (gcloud.compute.instances.create) Could not fetch resource: --- code: ZONE_RESOURCE_POOL_EXHAUSTED errorDetails: - help: links: - description: Troubleshooting documentation url: https://cloud.google.com/compute/docs/resource-error - localizedMessage: locale: en-US message: A e2-small VM instance is currently unavailable in the us-central1-a zone. Alternatively, you can try your request again with a different VM hardware configuration or at a later time. For more information, see the troubleshooting documentation. - errorInfo: domain: compute.googleapis.com metadatas: attachment: '' vmType: e2-small zone: us-central1-a zonesAvailable: '' reason: resource_availability message: The zone 'projects/qwiklabs-gcp-04-ac0ef6ae2d54/zones/us-central1-a' does not have enough resources available to fulfill the request. Try a different zone, or try again later.

Duarte Bruno · 約2ヶ月前にレビュー済み

Terrible experience - it was impossible to create required instances within the specific zone. Other steps/tasks were accepted/accomplished, resulting in 70%. Credit wasted.

Janousek Pavel · 約2ヶ月前にレビュー済み

The lab instructions were clear, but I was unable to complete the hands-on portion because the specified us-central1-a zone repeatedly returned ZONE_RESOURCE_POOL_EXHAUSTED. Attempting another zone resulted in a gcp.resourceLocations constraint error. The issue appears to be with resource availability/location restrictions in the temporary lab environment rather than the lab steps themselves.

Sarkar Samridh · 約2ヶ月前にレビュー済み