Description of problem:
we have seen a case in which a resume command to libvirt (short operation) is stuck on libvirt forever which put the vm on a stuck status on vdsm/rhevm as well fore ever- vdsm should have a protraction at least against this actions
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.we have seen this issue happening on https://bugzilla.redhat.com/show_bug.cgi?id=625100
*** Bug 622488 has been marked as a duplicate of this bug. ***
In case the create operation (VDSM -> LIBVIRT) does not return (as in the above described scenario).
It should have beed solved by the API timeout mechanism in libvirt, but this mechanism does not support such scenarios.
In order to solve this we need to build an internal timeout mechanism in VDSM->Libvirt communiction, it looks like impossible to do so since libvirt does not support cancel (and clean up) of creation command.
I only just noticed the needinfo set for me on this BZ, sorry for the delay. This situation should be solved by the work we're doing for BZ 692663.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.