The zone 'projects/XXXXX/zones/us-east1-b' does not have enough resources available...

[Matt R]

The zone 'projects/eve-ng-239513/zones/us-east1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.

I am new to Google Cloud. Experimenting with using it for running a network lab simulation software.  I have been stopping the VM when I don't need it.  First few days seemed to work well... but today and yesterday I have gotten this error when I try to start my small VM (2cores 8GB RAM).  I have a single instance for this, not preemptible, (it is the free credit.)  But I don't get it...  Seems like this workload should be extremely easy to spin up in any zone.   Moving it to another zone is a pain and this is not a multi-VM application.   Does not bode well for Google Cloud as a product to be used for bigger and better things.   

Is there a way to see available resources in the different zones? 

[Matt R]

It did finally work now (later) 8pm. EST.  It did not work mid-day today and mid-day yesterday. 

[Anthony (Google Cloud Support)]

Hi Matt,

It is unfortunate that you had faced that issue. 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. However in order to avoid an event such as this in the future, I recommend that you should deploy your workloads in multiple zones or regions in order to reduce the likelihood of an outage. You should look at the following dashboard to view updates on any issues occurring on GCP.

I do implore you to read the following documentation on Designing Robust Systems and Building scalable and resilient applications.

In regards to your inquiry about if there a way to see available resources in the different zones, currently this feature is available at this moment. However, if you would like this function to be available in the near future, I will encourage you to create a feature request in regards to this. I would like to point out that feature requests do not have an ETA as to when they will be processed or completed.