Timeout option can kill active connections that are still transferring data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
Undecided
|
Free Ekanayaka | ||
Smart Package Manager |
Fix Released
|
Undecided
|
Gustavo Niemeyer | ||
smart (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The timeout option being used in smart is about the whole lifetime of the connection, regardless if it's idle or not. If you are downloading a big package over a slow link, it can kill your download:
Failed to download packages:
http://
In the example above, the download was still active, i.e., bytes were being transferred.
The Landscape Team has proposed an SRU to fix this bug in intrepid and jaunty.
Statement explaining the impact
=======
This bug affects anybody with a slow but yet working connection.
How the bug has been addressed
=======
Passing a LOW_SPEED_LIMIT=1 parameter to the relevant libcurl call.
Detailed instructions how to reproduce the bug
=======
It can be reproduced artificially by inducing a timeout by means of traffic shaping. It has been done by the Landscape QA engineer and the fix is confirmed to work as expected.
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
tags: | added: needs-testing |
description: | updated |
tags: | added: ubuntu |
Changed in smart: | |
milestone: | 1.3 → 1.2.1 |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
Changed in smart: | |
status: | Fix Committed → Fix Released |
This has been fixed in revision 867 in Smart's trunk.