Bug 1242373

Summary:	[RFE] - Should be able to set operation timeout at command level from oVirt engine
Product:	[oVirt] vdsm	Reporter:	Shubhendu Tripathi <shtripat>
Component:	RFEs	Assignee:	Ravi Nori <rnori>
Status:	CLOSED DEFERRED	QA Contact:	movciari
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bazulay, bugs, daniel.helgenberger, lsurette, mgoldboi, mperina, oourfali, pkliczew, pstehlik, rbalakri, srevivo, ycui, ykaul
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	oourfali: ovirt-future? mgoldboi: planning_ack+ oourfali: devel_ack? pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-07 18:31:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1203701

Description Shubhendu Tripathi 2015-07-13 08:24:26 UTC

Description of problem:
Should be able to set operation timeout at command level from oVirt engine

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create maximum possible (256) volume snapshots for a gluster volume
2. Try to delete all the snapshots for the volume using "Delete All" option under Snapshots sub-tab of Volumes main tab


Actual results:
Engine event log shows a network error as command timed out because VDSM command took lot of time to complete.

Expected results:
Should be able to set command timeout at command level, so that admin can judicially select value for a specific call and command is successfully executed.

Additional info:
NA

Comment 1 Yaniv Kaul 2015-11-22 19:58:39 UTC

I'd argue that the right thing to do here is for the command to be able to report progress and liveness - based on both, the timeout can be automatically adjusted.
Oved?

Comment 2 Piotr Kliczewski 2015-11-23 08:02:26 UTC

I think that we could use event infrastructure we have to report how execution progresses. We would need to cover network issues scenarios but it looks doable without setting any timeout.

Comment 3 Oved Ourfali 2015-12-22 08:03:38 UTC

Moti - consider that as well in the coco changes in 4.0.

Comment 4 Oved Ourfali 2016-04-22 14:32:27 UTC

As we're still looking into the right way, not sure it will be part of 4.0. 
Removing the devel ack.