Styjun

After executing

gcloud compute instances move instance-ba --zone us-east1-b --destination-zone us-east1-c

and waiting for about 5 minutes the following error was thrown

Moving gce instance instance-ba...failed.
ERROR: (cloud.compute.instances.move) Code: '6562453592928582321'

and the instance was gone from the web interface as well as from zone us-east1-b and us-east1-c

I tried to start the instance with

cloud compute instances start instance-ba --zone us-east1-b

and

cloud compute instances start instance-ba --zone us-east1-c

but none was working.

Thank you in advance for your help.
I have to say that this instance is quite important and I appreciate every input to solve this issue.

Edit

In the Stackdriver Logging I am seeing the following commands executed alternating:

• Compute Engine setDiskAutoDelete us-east1-b:instance-ba


• compute.instances.setDiskAutoDelete

As it seems the instance has been deleted from us-east1-b but not transferred to us-east1-c.

I do not see any error at all. All logs have severity "INFO" or lower.

Edit 2

I recall my steps which preceeded the moving error as follows

• I tried adding a second Tesla P100 to my instance which gave at startup the error that the resources are not enough to fulfill the request


• I tried moving the instance which gave the "TERMINATED" error so I


• tried to reset the machine with the reset command which gave the "instance not ready" error


• I removed the second Tesla P100 so that I could start the machine


• I did the restart command over and over until it worked and the machine was able to start


• Since I needed a second GPU I tried to moved this instance (without the second GPU) from us-east1-b to us-east1-c which finally did not work and gave the error

Edit 3

After some research I found that the procedure actually made a snapshot from my instance and the data is not lost.

However I will keep this question updated concerning the error and the response to it from google.

According to the documentation, you have a short specification for when to use the manual or the automatic move. As the procedure says, use the manual move when:

"Your VM is not RUNNING."

"You are moving your VM to a different region and your VM belongs to a subnetwork."

"Your instance has GPUs or local SSDs attached."

In your case, you had one GPU attached to your instance. So the correct way to move it is the following:

1. Stop your instance


2. Edit the instance, on the “Machine type” click customize and select “none” numbers of GPU. More details here.


3. Start your instance


4. Use the gcloud command to move the instance between zones:

$ gcloud compute instances move example-instance --zone us-central1-a --destination-zone us-central1-f

5. Once the instance is migrated stop it again.


6. Add the GPU and start the instance.

Keep in mind that every zone has different GPUs available and new projects have limits for GPUs.

"To protect Compute Engine systems and users, new projects have a global GPU quota, which limits the total number of GPUs you can create in any supported zone. When you request a GPU quota, you must request a quota for the GPU models that you want to create in each region, and an additional global quota for the total number of GPUs of all types in all zones."