ZONE_RESOURCE_POOL_EXHAUSTED status when Compute Engine instances are started

663 views
Skip to first unread message

M Surasinghe

unread,
Oct 31, 2018, 12:10:30 PM10/31/18
to gce-discussion

Taame (Google Cloud Support)

unread,
Oct 31, 2018, 4:52:57 PM10/31/18
to gce-discussion
Hi, 
 
When you mentioned that you changed your project name did you receive any other error messages in that process, because the shared error message you provided is more related to the fact that your zones 'us-west1-b' and 'us-east1-b' have no resources available. 
 
Our goal is to make sure that there are available resources in all zones. This type of issue is rare. When a situation like this occurs, or is about to occur, our team is notified immediately and the issue is investigated and mitigated.
 
I tried to create instances in the mentioned problematic zones to make sure if the issue is still persisting, but I was able to create and start them. 
 
On the other hand, I want to share a detailed procedure for moving instances between zones to help you start your instance in another zone with available resources to see if you have the same issue again. The easiest way would be to use the 'gcloud compute instances move' command described there. Please, however, check out the requirements and precautions related to moving instances to avoid issues during moving your instances.

Tech Services

unread,
Oct 31, 2018, 6:52:45 PM10/31/18
to gce-discussion
Ive had this issue and I managed to work around it by not assigning a public IP - set it to "none".
Once the VM is created you can then assign an IP but YMMV.

Dave

Bee Bee

unread,
Nov 1, 2018, 4:52:43 AM11/1/18
to gce-discussion
hi Dave, 

I followed your method and successfully created the VM,
 however must i choose a "Reserve static address" 
in order to successfully connect to the VM? 
It seems will extra charge for each static address, can i get a ephemeral ip instead?
thank you very much.

Bee

Tech Services於 2018年11月1日星期四 UTC+8上午6時52分45秒寫道:

Tech Services

unread,
Nov 1, 2018, 5:05:34 AM11/1/18
to gce-discussion
Yes, static IP's cost money but you should be able to attach either static or ephemeral public IP's now.

Bee Bee

unread,
Nov 1, 2018, 5:10:26 AM11/1/18
to gce-discussion
The problem solved, i could choose either the ephemeral or static after the VM created. Thank you very much.
However, did i need to do this procedures every time starting from now? 
Or this problems will solved automatically when the "Zone Resources" was fine?
It seems like a problems of the allocation of the IP address instead of out of Zone Resources..

Bee

Tech Services於 2018年11月1日星期四 UTC+8上午6時52分45秒寫道:
Ive had this issue and I managed to work around it by not assigning a public IP - set it to "none".

Tech Services

unread,
Nov 1, 2018, 5:25:52 AM11/1/18
to gce-discussion
I doubt very much that the zone is out of resources, I assume they will roll out a fix at some stage and hopefully make the error reporting more relevant to the actual issue.

Kakuda Kachchayana

unread,
Apr 24, 2019, 2:27:51 PM4/24/19
to gce-discussion
Reply all
Reply to author
Forward
0 new messages