After cloudstack canceled volume live migration, VMWare still keeps on migrating this volume => Cloustack keeps old/wrong location of volume.

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
API, Volume
~~~

##### CLOUDSTACK VERSION

~~~
4.17.1.0
~~~

##### CONFIGURATION

VMWare vSphere

##### OS / ENVIRONMENT

##### SUMMARY

I tried to live-migrate a 4TB-volume via following command in cloudmonkey.
But after the given threshold of 120 minutes ("global settings" -> "job.cancel.threshold.minutes") this jobs has been canceled by cloudstack:
> "jobresult": {
> "errorcode": 530,
> "errortext": "Unable to serialize: Job is cancelled as it has been blocking others for too long"

VMWare had new/correct location of volume, but cloustack keeps old/wrong location of volume.

##### STEPS TO REPRODUCE

~~~
* For simmulating, set "global setting" "job.cancel.threshold.minutes" timeperode to a very small value, or adjust volume-size
* Migrate a volume to another storage, what should be canceled during specified timeperode (Also via GUI possible):
CMK> migrate volume livemigrate=true storageid=xxxxg volumeid=xxxxxx
~~~

##### EXPECTED RESULTS

~~~
This migration in cloudstack has been "canceled" correctly, but migration in VMWare should have also been aborted.
~~~

##### ACTUAL RESULTS

~~~
VMWare finished the volume livemigration, but cloudstack does not know this new location.
If that corresponding virutal machine is shut down and startet again. this vm will be "orchestrated" with the wrong volume-informations and vm will not boot any longer.
~~~

Cloudstack-Error:
> Unable to orchestrate start VM instance {id: "xxxx", name: "i-xxx-xxxxx-VM", uuid: "xxxx", type="User"} due to [Unable to start instance 'xxxxx' (xxxx), see management server log for details].