Opinie (Building a High-throughput VPN)
16135 opinii
resources are not available.
Vidyasagar R. · Sprawdzono ponad 2 lata temu
Kelvyn D. · Sprawdzono ponad 2 lata temu
Kamisetty M. · Sprawdzono ponad 2 lata temu
Pourab Bhattacharyya .. · Sprawdzono ponad 2 lata temu
The lab asks to create a subnet in region us-east1, but this region is not allowed in the project's Resource Location policy, resulting in this error: ERROR: (gcloud.compute.networks.subnets.create) Could not fetch resource: - Location REGION:us-east1 violates constraint constraints/gcp.resourceLocations on the resource projects/qwiklabs-gcp-01-a24080d988dd/regions/us-east1/subnetworks/cloud-east.
Óscar S. · Sprawdzono ponad 2 lata temu
Zaulfiqar A. · Sprawdzono ponad 2 lata temu
last command is not working
Zaulfiqar A. · Sprawdzono ponad 2 lata temu
marian v. · Sprawdzono ponad 2 lata temu
Devaraj V. · Sprawdzono ponad 2 lata temu
Devaraj V. · Sprawdzono ponad 2 lata temu
George F. · Sprawdzono ponad 2 lata temu
You can't finish this lab due to a constraint. Whenever you try to deploy any resource on the us-east1 region, the gcp.resourceLocations constraint will raise and won't allow you to create it. So, in a few words, the same lab doesn't give you the entire permission to finish it. Needs to be fixed so it allows you to create resources on other regions rather than just in us-central1
Carlos A. · Sprawdzono ponad 2 lata temu
Please change instructions to use e2 machine types to increase the chance of the machine type being available.
Jasper v. · Sprawdzono ponad 2 lata temu
Omar M. · Sprawdzono ponad 2 lata temu
Was unable to complete due to the zone not having enough resources to create the necessary VMs
Jonas B. · Sprawdzono ponad 2 lata temu
ERROR: (gcloud.compute.networks.subnets.create) Could not fetch resource: - Location REGION:us-east1 violates constraint constraints/gcp.resourceLocations on the resource projects/qwiklabs-gcp-00-d2cbab770d74/regions/us-east1/subnetworks/cloud-east.
Gennadiy M. · Sprawdzono ponad 2 lata temu
Perfect
eliseo b. · Sprawdzono ponad 2 lata temu
Michael S. · Sprawdzono ponad 2 lata temu
Kent H. · Sprawdzono ponad 2 lata temu
Tapan H. · Sprawdzono ponad 2 lata temu
Sentot S. · Sprawdzono ponad 2 lata temu
Tapan H. · Sprawdzono ponad 2 lata temu
Couldn't make connection: "connect failed: Operation now in progress". Tried to check that everything is as should, couldn't find anything wrong.
Henri W. · Sprawdzono ponad 2 lata temu
Imran A. · Sprawdzono ponad 2 lata temu
1 problem is us-central1-a resource pool is really often exhausted when it comes to n1 machines types nowadays, I feel like at least. If I change the zone from the predefined one I can create the VM but the solution isn't accepted, so I had to recreate a different machine type in the same zone to make this automatic grading system accept my solution. It would be great if there would be some description about what is an accepted and what is a not accepted solution, so me first trying to recreate the same machine type in a different zone (which should not be a problem for this throughput testing) is not accepted, but creating the smaller machine (e2-small in this case) is accepted but it does undermine the throughput testing because the lower amount of vCPUs given by e2-small.
Márk R. · Sprawdzono ponad 2 lata temu
Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.