VM Instance not starting - does not have enough resources available to fulfill the request.

[IT-Mate Solutions]

Hi All,

Our website hosted on G-Cloud was running slow.

So I wanted give the instance a reboot.

Therefore I stopped and tried to start but now when starting the instance is not booting.

Error Message:

Operation type [start] failed with message "The zone 'projects/famous-augury-275202/zones/australia-southeast1-c' does not have enough resources available to fulfill the request. Try a different zone, or try again later

Very Frustrating.

Any assistance will highly appreciated. 

Thanks,

Rizni

[Alejandro Lorea Sanchez]

I just answered a very similar question. You could take a look and see if it helps you as well. This is the quoted answer: 

“This issue is well known and has been seen in this question (and a few others). We can see the answer explains “Its recommended to deploy and balance your workload across multiple zones or regions1 to reduce the likelihood of an outage, by building resilient and scalable architectures.” 

And explained in the documentation: “Resource errors only apply to new resource requests in the zone and do not affect existing resources. Resource errors are not related to your Compute Engine quota and only apply to the resource you specified in your request at the time you sent the request, not to all resources in the zone.”

To solve it you can try a few options from either the forum: “If you want an immediate solution, create a snapshot 2, then create an instance from the snapshot with different zone or region 3.”

“Resolution:

• Try to create the resources in another zone in the region or in another region.

• Because this situation is temporary and can change frequently based on fluctuating demand, try your request again later.

• Try to reduce the number of resources you are requesting. For example, it's usually easier to get a VM with less GPUs, disks, vCPUs, and/or memory. Additionally, if your request is for multiple VMs, it's easier to get a smaller number of VMs. A reduction in the number of resources you are requesting might let your request proceed.

• Try to change the type of resources you are requesting. For example, it might be easier to get VMs with older CPU platforms. A change to the type resource you are requesting might let your request proceed.

• To prevent this error, create Compute Engine reservations when the resources you need are available to reserve them within a zone. Reservations help ensure that resources are available whenever you need them, so keeping reservations of resources you need can help prevent this error.

• If you are trying to create Spot VMs (or legacy preemptible VMs), remember that these VMs are spare capacity, which is unplanned and volatile, so they might not be obtainable at peak demand periods. Consequently, Spot VMs are only recommended for workloads with flexible time, location, and VM-configuration requirements. You can help prevent this error for Spot VMs by following the best practices to make your workload more flexible. If this error persists, use standard VMs instead.

• If you were unable to resolve the error using any of the preceding instructions, try Getting support.“

Finally, try to follow the Best practices suggested, and though it is up to you, try to follow this  step while creating your machine “Optional: Change the Zone for this VM. Compute Engine randomizes the list of zones within each region to encourage use across multiple zones.” and the guide on Tips for designing resilient systems and use of load balancer if you haven’t already to avoid this issue in the future.”