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
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?
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.
Moti - consider that as well in the coco changes in 4.0.
As we're still looking into the right way, not sure it will be part of 4.0. Removing the devel ack.