Is there any way to recover it? Does google delete instances in this case automatically?
Thanks
Google, as for now, does not offer an ability to recover deleted instances at all. They did receive several feedbacks on this issue (one of them is here) to enable recovering deleted instances or to put deleted instances in a bin for a short period of time, but they leave those ideas "under review" and don't plan to implement it any time soon.
Related
As it is described on the title, I cannot reach a notebook instance for 3 days continiously. I also have this issue occasionally.
Anytime I try, It prompts
does not have enough resources available to fulfill the request. Try a
different zone, or try again later.
And it never became available at all! Any suggestions? I thought to move instance to another region but I am afraid this issue can be encountered on other regions too which is not a solid solution at least.
I would suggest you to try creating the instance in another region/zone.
It would also be useful to know in which zone are you trying to create the instance.
Zones like south-asia1-a/b/c (Mumbai) are always used at their full capacity and rarely have enough resources for creating new instances. There's another post with a similar situation, with a more detailed answer that may solve or find a workaround to your specific case here. Please let me know if this solves your issue.
not have enough resources available to fulfill the request try a different zone
All of my machines in the different zone
have the same issue and can not run.
"Starting VM instance "home-1" failed.
Error:
The zone 'projects/extreme-pixel-208800/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later."
I am having the same issue. I emailed google and figured out this has nothing to do with quota. However, you can try to decrease the need of your instance (eg. decrease RAM, CPUs, GPUs). It might work if you are lucky.
Secondly, if you want to email google again, you will get the message sent from the following template.
Good day! This is XX from Google Cloud Platform Support and I'll be
glad to help you from here. First, my apologies that you’re
experiencing this issue. Rest assured that the team is working hard to
resolve it.
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.
We recommend deploying and balancing your workload across multiple
zones or regions to reduce the likelihood of an outage. Please review
our documentation [1] which outlines how to build resilient and
scalable architectures on Google Cloud Platform.
Again, we want to offer our sincerest apologies. We are working hard
to resolve this and make this an exceptionally rare event. I'll be
keeping this case open for one (1) business day in case you have
additional question related to this matter, otherwise you may
disregard this email for this ticket to automatically close.
All the best,
XXXX Google Cloud Platform Support
[1] https://cloud.google.com/solutions/scalable-and-resilient-apps
So, if you ask me how long you are expected to wait and when this issue is likely to happen:
I waited for an average of 1.5-3 days.
During the weekend (like from Friday to Sunday) daytime EST, GCP has a high probability of unavailable resources.
Usually when you have one instance that has this issue, others too. For me, keep trying in different region waste my time. (But, maybe it just that I don't have any luck)
The error message "The zone 'projects/[...]' does not have enough resources available to fulfill the request. Try a different zone, or try again later." is always in reference to a shortage of resources in a zone.
Google recommends spreading your workload across different zones to reduce the impact of these issues on your workload. Otherwise, there isn't much else to do other than wait or try another zone/region
Faced this Issue yesterday [01/Aug/2020] when GCP free credit was over and below steps helped to workaround this.
I was on asia-south-c zone and moved to us zone
Going to my Google Cloud Platform >>> Compute Engine
Went to Snapshots >>> created a snapshot >>> Select your Compute Engine instance
Once snapshot was completed I clicked on my snapshot.
Ended up under "snapshot details". There, on the top, just click create instance. Here you are basically creating an instance with a copy of your disk.
Select your new zone, don't forget to attach GPUs, all previous setting, create new name.
Click create, that's it, your image should now be running in your new zone
No worry of losting configuration as well.
My google cloud VM hard disk got full. So I tried to increase its size. I have done this before. This time things went differently. I increased the size. But the VM was not picking up the new size. So I stopped VM. Next thing I know, my VM got deleted and recreated, my hard disk returned to previous size with all data lost. It had my database with over 2 months of changes.
I admit I was careless not to backup. But currently my concern is, is there a way to retrieve the data. On Google Cloud, it shows $400 for Gold Plan which includes Tech Support. If I can be certain that they will be able to recover the data, I will am willing to pay. Does anyone know if I pay $400, the google support team will be able to recover the data?
If there are other ways to recover data, kindly let me know.
UPDATE:
Few people have shown interest in investigating this.
This most likely happened because by default "Auto-delete boot disk" option is selected which I was not aware of. But even then, I would expect auto-delete to happen when I delete the VM, not when I simply stopped it.
I am attaching screenshot of all activities that happened after I resized the boot partition.
As you can see, I resized the disk at 2:00AM.
After receiving resize successful message, I stopped the VM.
Suddenly at 2:01, VM got deleted.
At this point I had not checked notifications, I simply thought, it stopped. Then I started VM hoping to see new resized disk.
Instead of starting my VM, new VM was created with new disk and all previous data was lost.
I tried stopping and starting VM again. But the result was still the same.
UPDATE:
Adding activities before the incident.
It is not possible to recover deleted PDs.
You have no snapshots either?
The disk may have been marked for auto-delete.
However, this disk shouldn't have been deleted when the instance was stopped even if it was marked for auto-delete.
You can also only recover a persistent disk from a snapshot.
In a managed instance group, when you stop an instance, health check fails and the MIG deletes and recreates an instance if autoscaler is on. The process is discussed here. I hope that sheds some light if that is your use case.
I am receiving the following when I try to add new AWS accounts to my newly created organization. Any thoughts on how to tackle this problem?
Make sure that your account has a complete billing profile, including payment information. If that is the case, and you are still having issues, AWS support will be able to help you identify the issue.
If this error occurs, wait for few minutes and retry. If it comes again contact AWS support. They will fix the issue mostly in 24hours time.
There is a clear message on the top, that your organization is in initialization status. Because of that you should wait until it's done initializing (in some cases it could take about an hour) and try again. AWS Documentation states (see step #7. Create), that
If you get an error that indicates that you can't add an account
because your organization is still initializing, wait one hour and try
again.
Therefore there is no need to contact a support for this kind of problems.
I had last semester a university course where I used AWS to do the homework, and later I deleted all instances, all volumes, everything. But it for some reason still counts hours (for now without charging me).
But I would like to know how can I disable every possibility to get charged, just in case I forgot something (cannot find something)
As stated I don't want to use their services anymore, so a brute-force account delete\disable is the best option for me.
Just contact AWS and request them to close it.
https://aws.amazon.com/support/