Bug 1563278

Summary: transfer image - client inactivity timeout is too short and can't be configured from api
Product: [oVirt] ovirt-engine Reporter: Daniel Erez <derez>
Component: BLL.StorageAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Evelina Shames <eshames>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: aefrat, bthurber, bugs, derez, ebenahar, rjones, ylavi
Target Milestone: ovirt-4.2.3Flags: rule-engine: ovirt-4.2+
ylavi: exception+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-11 06:51:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1586198    
Attachments:
Description Flags
upload_with_inactivity_script none

Description Daniel Erez 2018-04-03 13:54:07 UTC 
As part of image transfer monitoring in the engine, we have a client inactivity timeout, which abort the transfer after a defined time - specified by TransferImageClientInactivityTimeoutInSeconds config value.

When using the sdk for transfer, for certain usages and environment, this timeout could be too short or merely not useful. Hence, the value should be increased by default, and configurable through the API.
Comment 2 Avihai 2018-05-10 06:15:00 UTC 
Created attachment 1434202 [details]
upload_with_inactivity_script
Comment 7 Avihai 2018-05-10 12:03:35 UTC 
I'm verifying this bug as functionality looks ok.

Please answer 2) in previous comment and advise with new issue should be opened or script changed 

Verified on :
4.2.3.5-0.1.el7
ovirt-imageio-proxy-1.3.1.2-0.el7ev.noarch
ovirt-imageio-daemon-1.3.1.2-0.el7ev.noarch
Comment 10 Sandro Bonazzola 2018-05-11 06:51:25 UTC 
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.