Bug 121071

Summary:	up2date doesn't fall back to other mirrors if one fails
Product:	[Fedora] Fedora	Reporter:	David Woodhouse <dwmw2>
Component:	up2date	Assignee:	Bret McMillan <bretm>
Status:	CLOSED CANTFIX	QA Contact:	Fanny Augustin <fmoquete>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	mattdm, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-29 14:34:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	121179, 124619

Description David Woodhouse 2004-04-16 20:26:35 UTC

Description of problem:

On a PPC machine, up2date has this in its sources file:

yum-mirror fedora-core-rawhide 
http://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide

Sometimes an incomplete mirror mirror.hiwaay.net is selected, which
does not carry PPC RPMS. If this happens, up2date fails. Instead,
up2date should fall back to another mirror.

Comment 1 Andrew D. Stadler 2004-09-06 21:15:27 UTC

Twice now, up2date has selected a mirror that cannot be contacted. 
For example, right now I'm sitting on
http://mirror.eas.muohio.edu/fedora/linux/...
and it's not coming up.  It should have an option to try a different
mirror.  (the workaround, to completely quit and restart up2date,
seems to work fine)

Also, if I enter http://mirror.eas.muohio.edu/ into Mozilla, it
*immediately* says the host "could not be found".  Why does up2date
hang in the same scenario?

Comment 2 petrosyan 2004-10-16 15:17:47 UTC

*** Bug 132373 has been marked as a duplicate of this bug. ***

Comment 3 Matthew Miller 2005-04-26 15:18:08 UTC

Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 4 John Thacker 2006-10-29 14:34:12 UTC

Note that FC1 and FC2 are no longer supported even by Fedora Legacy, and FC3 and
FC4 are supported by Fedora Legacy only for security issues.  Please retest this
bug against a still supported version and retest.  If this still occurs on FC3
or FC4 and is a security issue, please reopen the bug and assign it to that
version and Fedora Legacy.  If it occurs on RHEL, please change to that product
and the appropriate version.

Note that up2date has been replaced by pirut/pup for FC5 and FC6, the only
fully-supported versions of Fedora Core.  Please test pirut for software updates
and file bugs as appropriate.