fabeulus opened a new issue, #7168:
URL: https://github.com/apache/cloudstack/issues/7168
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API, Volume
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.17.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
VMWare vSphere
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
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 hat new/correct location of volume, but cloustack keeps old/wrong
location of volume.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
* 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
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
This migration in cloudstack has been "canceled" correctly, but migration in
VMWare should have also been aborted.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
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].
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
