How to interrupt the migration task during CAS/UIS VM migration process

Null

When the customer is cloning the virtual machine, they first shut down the virtual machine, then create the clone task. However, the cloning process got stuck due to some reasons, such as a very large amount of data, resulting in a long cloning time. During the cloning process, the virtual machine cannot be started. At this time, the task cannot be manually deleted from the front end, and can only be accessed through SSH to the CVM backend to manually delete the corresponding cloning process and interrupt the process.

SSH to CVM backstage, the operation process is as follows:

1. Find the clone process ID according to the cloned virtual machine name. In this case, the virtual machine name is "clone".

root@cvknode:~# ps -ef | grep clone

root 100219 46328 18 18:30 ? 00:00:07 cp -f /vms/12q/clone /vms/images/clone_clone

root 100651 107476 0 18:31 pts/2 00:00:00 grep --color=auto clone

2. Record the corresponding ID number and terminate the process using the kill command:

root@cvknode:~# kill -9 100219

-bash: kill: (100219) - No such process

3. Use the ps command to check if the process still exists:

root@cvknode:~# ps -ef | grep clone

root 101174 107476 0 18:31 pts/2 00:00:00 grep --color=auto clone

4. Restart Tomcat and refresh the front-end page:

root@cvknode:~# service tomcat8 restart

* Stopping Tomcat servlet engine tomcat8                                           [ OK ] 

* Starting Tomcat servlet engine tomcat8 

According to the above instructions, manually killing the clone process can restore the virtual machine.