Bug 625343 - [RFE] vdsm should have timer for the short operations sent to libvirt
Summary: [RFE] vdsm should have timer for the short operations sent to libvirt
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Federico Simoncelli
QA Contact:
Whiteboard: infra
Keywords: FutureFeature, SubFeature
: 622488 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-19 06:42 UTC by Moran Goldboim
Modified: 2013-03-12 16:00 UTC (History)
8 users (show)

Clone Of:
Last Closed: 2013-03-12 16:00:15 UTC

Attachments (Terms of Use)

Description Moran Goldboim 2010-08-19 06:42:54 UTC
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):

How reproducible:

Steps to Reproduce:
1.we have seen this issue happening on https://bugzilla.redhat.com/show_bug.cgi?id=625100
Actual results:

Expected results:

Additional info:

Comment 2 Barak 2010-11-21 16:11:42 UTC
*** Bug 622488 has been marked as a duplicate of this bug. ***

Comment 3 Barak 2010-11-28 17:00:23 UTC
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.

Comment 4 Dave Allan 2011-06-23 02:23:23 UTC
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.

Comment 5 Itamar Heim 2013-03-12 16:00:15 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

Note You need to log in before you can comment on or make changes to this bug.