Bug 1185553

Summary:	dnf: connection timeout is too high
Product:	[Fedora] Fedora	Reporter:	Zbigniew Jędrzejewski-Szmek <zbyszek>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	akozumpl, jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-26 11:21:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zbigniew Jędrzejewski-Szmek 2015-01-24 16:11:32 UTC

Description of problem:
Sometimes dnf cannot connect to a mirror. After some time it tries with the next mirror, after printing something like "Connection timed out after 120001 milliseconds". A timeout of 120s for a connection is just too big. If a connection to a server does not succeed in 1s it probably isn't worth using it anyway. I think a timeout of 3s would be suitable and reduce the pain caused by non-responsive mirrors.

[MIRROR] colord-libs-1.2.8-1.fc22.x86_64.rpm: Curl error: Timeout was reached for ftp://mirrors.zimcom.net/pub/fedora/linux/development/rawhide/x86_64/os/Packages/c/colord-libs-1.2.8-1.fc22.x86_64.rpm [Connection timed out after 120001 milliseconds]

Version-Release number of selected component (if applicable):
dnf-0.6.3-3.fc22.noarch

Comment 1 Honza Silhan 2015-01-26 11:21:07 UTC

Hi, it will be configurable.

*** This bug has been marked as a duplicate of bug 1175466 ***