Bug 1563278 - transfer image - client inactivity timeout is too short and can't be configured from api
Summary: transfer image - client inactivity timeout is too short and can't be configur...
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.2
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: ovirt-4.2.3
: ---
Assignee: Daniel Erez
QA Contact: Evelina Shames
Depends On:
Blocks: 1586198
TreeView+ depends on / blocked
Reported: 2018-04-03 13:54 UTC by Daniel Erez
Modified: 2018-06-05 18:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-11 06:51:25 UTC
oVirt Team: Storage
rule-engine: ovirt-4.2+
ylavi: exception+

Attachments (Terms of Use)
upload_with_inactivity_script (5.77 KB, text/x-python)
2018-05-10 06:15 UTC, Avihai
no flags Details

System ID Priority Status Summary Last Updated
oVirt gerrit 89767 master POST ImageTransfer - adding 'clientInactivityTimeout' property 2018-04-09 13:07:01 UTC
oVirt gerrit 89768 master MERGED core: TransferImage - configurable client timeout 2018-04-23 18:07:05 UTC
oVirt gerrit 89772 master MERGED core: increase TransferImageClientInactivityTimeoutInSeconds value 2018-04-04 11:05:48 UTC
oVirt gerrit 90363 master MERGED restapi: Update to model 4.3.10 2018-04-17 06:27:18 UTC
oVirt gerrit 90364 ovirt-engine-4.2 MERGED restapi: Update to model 4.2.32 2018-04-17 08:01:43 UTC
oVirt gerrit 90556 ovirt-engine-4.2 MERGED core: TransferImage - configurable client timeout 2018-04-25 08:32:56 UTC

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]

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 :

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.

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