Hello everyone. I am currently working as a lab assistant in a university in Indonesia and are currently teaching GCP to about 450 students. We are using the Higher Education Grants system and mostly use us-central-1 region since the region looks like it has the cheapest prices available. However, as of today, we cannot acquire any resources from said region. Here is the error message:
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.
Is there anything that we can do? We currently try to redirect students to other regions or machine types. However, this does add complexity to the students to setup the machines all over again. Thank you very much for any help that will come
Hi, we have also a e2-micro VM and after stoping it to reboot it… since yesterday is impossible, We get this error message:
Failed to start instance-1: 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.
Is google going to increase resources in this zone? How could I see which zones are with free resources at least to move our VM ?
Hmm, I was able to launch a c2-standard-8 without any problems. The e2 instances still don’t work. Maybe google is pushing us towards the more expensive SKUs!
Happy Thanksgiving!
I am experiencing a similar issue. I am currently working on a cloudskillsboost.google challenge.
While trying to spin up a f1-micro instance I get the following error:
A f1-micro VM instance is currently unavailable in the us-east1-b 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.
Hi, unfortunately, zones are permanent when you create the instances. You can’t edit it. If the VPS doesn’t have much data, I say make a new instance in the West region. That worked for me.
Me too…busy with a LAB where I need to raise a n1-standard-1 (1vCPU, 3.75 GB memory) but get the VM hardware unavailable…tried on 24th and 25th…am meant to be creating in us-central1-c have tried another machine type and us-central1-a same issue…I’m presuming it has something to do with Black Friday and maybe a temporary ban on creating vm’s associated with training LABs …but this is speculation on my part.
With the holidays this past week, most of the company off, I so happened to login on my off day and thats how I noticed one of our batch scripts stopped executing. We have a VM which auto gets created every 6 hours and it executes a docker image. Well, it stopped working since Wednesday due to this lack of resources on us-central1. Fortunately it won’t be anything super serious on our end, but what if it was?
It would be great if there was infrastructure behind the scenes on Google’s side that could do something like:
If VM creation on us-central1 fails for e2-highcpu-2 then
Attempt VM creation on us-west1 with e2-highcpu-2
