I have 4 vm instances in South-Asia region in two zones (south-asia-a & south-asia-c) out of three. I can't boot up all four instances due to below error regarding resources not available in current zone or region.
I can't move instances to other region, because public IP will change, in South-Asia region all zones shows same error.
Even tried to create new instance in different zone like south-asia-b, but same error.
The zone 'projects/some-projectname/zones/asia-south1-c' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
EDIT: Tried all three zones a,b,c of asia-south.
What can I do?
Yes I have face the same issue. I ended up switching to asia-south1-c. This is a recent error. I first encountered 1.5 weeks ago. If you must use asia-south1-a then you can raise a support ticket. Anyway, the issue should be fixed soon since many users are facing the same problem.
In case you have snapshots of the instances disks you can use the snapshots as an existing disk to create new instances in any region/zone. If you do not have a snapshot you cannot create now since the instance has to be running to do so.
Edit:
We are continuously adding more and more resources to avoid situations like this. If your workload is predictable long term, you may want to purchase commitment and reserve the resources you will use at a discount price.
Related
I am facing this issue from yesterday. This is the exact error: Failed to start feature-config: A e2-micro 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.
I had scheduled Google Compute Engine to TURN on & off at specific time using Instance scheduler but now I am locked out of it. I cannot even create a machine image to deploy on another zone
I changed the Machine Configuration. As from your answer I could figure out that resources might not be available for the US Central Zone possibly due to traffic. I changed configuration to - n2-highcpu-2 vCPU 2 & Memory -2 GB
At the end, it seems this was a general issue that multiple users experienced in us-central1 among other regions.
In this thread more is talked and it seems it got worse during the weekend.
As some suggestions in the comments, changing the zone/region/hardware can help but not always since this also depends on any constraints you may have.
As the error suggests, there aren't any available resources in that regions. I contacted GCP support after facing the same issue and got the following response:
Google Cloud Support, : Upon further checking, the reason that the e2-medium VM instance is currently unavailable is because there are limited VMs available to a specific zone and regions. Best we can do is to try another time or select a different zone so that the VMs that you desire to use will start. Rest assured that there is nothing wrong with your account and it was on the us-central1 zone who do not have available VMs you selected as of the moment.
If possible, try deploying to a different instance. For those who need an instance in us-central1 (for Qwiklabs?) might have to wait until more instances are available.
Similar issue here, but coming from a terraform apply. I've tried multiple zones and every one says both 'e2-small' and 'e2-micro' instances are unavailable. Seems google completely fumbled the "cloud game" here since AWS doesn't have this problem EVER! (not that I like using AWS, it's just "ick" compared to google).
I'm trying some stuff on Google Cloud and I have the following issue. Some days ago I created a Deep Learning VM with Compute Engine, with 8 vCPU and 1 Tesla K80 GPU. All worked fine, but now I want to try another GPU with different memory size. So, I deleted the VM instance (from Compute Engine -> VM instances) and I also deleted the deployment from Deployment manager. Nevertheless, when I try to create a new VM, I get an error message referring to the fact that I no more resources available and in fact, in the quotas page, I still see the GPU usage to 1 (with a limit of 1, that's why I can't create a new instance). Does anyone knows what could be the problem? Do I just have to wait? Thank you everyone!
If you receive a resource error (such as ZONE_RESOURCE_POOL_EXHAUSTED or ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS) when requesting new resources, it means that the zone cannot currently accommodate your request.
This error is due to the availability of Compute Engine resources in the zone, So, you could try to create the resources in another zone in the region or in another region.
You can search another available zone on this document: Available regions and zones
If possible, change the shape of the VM you are requesting. It's easier to get smaller machine types than larger ones. A change to your request, such as reducing the number of GPUs or using a custom VM with less memory or vCPUs, might allow your request to proceed.
Also, you can create reservations for Virtual Machine (VM) instances in a specific zone, using custom or predefined machine types, with or without additional GPUs or local SSDs, to ensure resources are available for your workloads when you need them.
Additionally, you can found more information to troubleshoot this issue in the following link
I am trying to create a server in Location Mumbai for past 2 months , I am getting Error in all 3 a,b,c zones.
When will the servers will be available in mumbai ?
I assume that you've got an error message like:
The zone 'projects/XXX/zones/asia-south1-x' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
while creating VM instances at asia-south1-a, asia-south1-b and asia-south1-c.
It's not an issue. Have a look at the documentation to find more details:
If you receive a resource error (such as ZONE_RESOURCE_POOL_EXHAUSTED
or ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS) when requesting new
resources, it means that the zone cannot currently accommodate your
request. This error is due to Compute Engine resource obtainability,
and is not due to your Compute Engine quota.
The reason for this behavior is resource availability which depends from users requests and therefore are dynamic.
There are a few ways to solve it:
Choose another zone for your instance.
Wait for a while and try to start your VM instance again.
Reserve resources for your VM by following documentation to avoid such issue in future:
Create reservations for Virtual Machine (VM) instances in a specific
zone, using custom or predefined machine types, with or without
additional GPUs or local SSDs, to ensure resources are available for
your workloads when you need them. After you create a reservation, you
begin paying for the reserved resources immediately, and they remain
available for your project to use indefinitely, until the reservation
is deleted.
I am getting ZONE_RESOURCE_POOL_EXHAUSTED error for all three asia-south1 region from last 24 hours. It is new gcp account created 4-5 days, and yesterday created project and am trying to launch new instance in asia-south1, but every time I am getting this error for all three zones.
I tried with my another organisation which I am using from last 1 years and able to launch instance in asia-south1. Not sure why this is happening for only new project.
The zone 'projects/<PROJECT_ID>/zones/asia-south1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
If you see 'ZONE_RESOURCE_POOL_EXHAUSTED' error meaning you are encountered with the temporary resource stock-out issue at that particular zone. This error is due to Compute Engine resource obtainability, and is not due to your Compute Engine quota.
When you start an instance (or change it) it requests resources like vCPU and memory and if there's not enough resources available in the zone you'll get an error message:
Error: The zone 'projects/thetourking/zones/asia-south1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
You can read more detailed information about that errors in this documentation.
There are various recommended workarounds:
Move your instances to another zone following this instructions.
Wait for a while and try to start your VM instance again because those issues are to be expected transiently.
Reserve zonal resources for your instances to avoid the same issue in the future. Keep in mind that reserving zonal resources requires an extra payment.
Instance group attempting to create an instance, but can't, with this error:
The zone 'projects/myproject/zones/us-central1-f' does not have enough resources available to fulfill the request
How do I fix this, and is it something I should be expecting from GCE on regular basis?
Thanks
In some rare occasions, some zones might not have enough resources available to fullfill a request. This is done to ensure that there are enough resources in each zone, to ensure that already installed users have enough of them to keep running their applications.
This type of issues are immediately noticed, and currently this is being investigated. For the moment, you can try to do one the following points:
Keep trying to do the deployment until the zone has enough resources.
Relax the requirements of the instance you are creating ( i.e. less CPU/Disk/Memory...)
Try to deploy to another zone within the same region, for example deploy to us-central1-a. You can see the full list of available zones/regions in this documentation
I would recommend you to go for the third option, as you will be able to create the instances immediately, with the resources you need, and you probably won't be affected by the zone change.