andrijapanicsb opened a new issue, #7847:
URL: https://github.com/apache/cloudstack/issues/7847
<!--
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 -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
NA
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
NA
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
NA
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When various long-running actions are done (VM migration, offline VM
migration, volume snapshot etc) - sometimes these long-lasting actions will
fail due to hitting a timeout setting(s) (large volumes, slow network, etc).
At the moment, we can see after how long the job has been cancelled (timed
out) - but it would be nice to improve logging to log particular global timeout
values that are in the game for the given job (wait, migratewait,
kvm.storage.offline.migration.wait, etc - whatever is used) - this way user can
easily see what to increase in Global Settings.
--
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]
