Bug 499653

Summary:	yum reports repo error while updating in 64 bit Fedora 10
Product:	[Fedora] Fedora	Reporter:	Raj Ramamoorthy <rramamoo>
Component:	mirrormanager	Assignee:	Matt Domsch <matt_domsch>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	ffesti, james.antill, jonstanley, matt_domsch, pmatilai, robatino, rramamoo, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-19 15:26:37 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:

Description Raj Ramamoorthy 2009-05-07 14:59:53 UTC

Description of problem:

Downloading Packages:
http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/Packages/gstreamer-python-0.10.12-1.fc10.x86_64.rpm: [Errno 4] IOError: <urlopen error (101, 'Network is unreachable')>


Version-Release number of selected component (if applicable):
Fedora 10 x86_64

How reproducible:
Everytime since last few days

Steps to Reproduce:
1.  Just type yum update in 64bit Fedora 10.
2.
3.
  
Actual results:
yum uses mirror site to update for all packages

Expected results:
yum should have got to the first site it has in the list if its available. We do not expect it to be down for too long.

Additional info:
My email id rramamoo and I am running Fedora 10 x86_64 on Lenovo laptop ThinkPad T500. I get this error from all networks I have used so far.

Comment 1 James Antill 2009-05-07 16:17:36 UTC

What is the bug here?

The above message is yum/httplib/etc. telling you the network is down ... is the network not down?

Also yum hasn't changed on Fed-10 for a long time now, so if there is a recent problem it's unlikely to be on the yum side.

Comment 2 Andre Robatino 2009-05-07 17:08:31 UTC

If it's a brand new F10 install, it could be glibc bug #459756 that caused DNS lookup problems.

Comment 3 Raj Ramamoorthy 2009-05-07 17:32:34 UTC

Network is not down. I am able to browse, email normally from the machone. Its a brand new install done on Monday May 4th, 2009. As far as I recall, all my yum updates and installs have gone to mirror site and any link to http://fedora.secsup.org/linux/releases/10/Everything/x86_64/os/*** has failed with same network error.  

The Fedora install is otherwise fully functional. The only irritant is the time delay for updates to begin as yum and package installers are waiting to get to the mirror after first timeout.

Is there a way to quickly remove this link from repo list and make the first mirror as my main link ? I can then check if problem is with glibc or something else ?

Comment 4 James Antill 2009-05-07 21:53:25 UTC

Ok, this sounds like a mirrormanger problem.

You could install yum-fastestmirror, and tell it to ignore that URL. There's also:

 http://skvidal.fedorapeople.org/misc/prune-by-regex.py

...to allow you to do the same thing. With Fed-10 you can also just go in /var/cache/yum/updates/mirrorlist.txt ... and remove the first line.

Comment 5 Matt Domsch 2009-05-08 04:33:05 UTC

I've forwarded the report to  morrowc who is the listed admin for this mirror, copying the problem reporter.

I note that from my home in Austin on Time Warner Cable, I can download the noted failing file just fine.  Could be a routing problem between the Red Hat office and secsup.org?

Comment 6 Matt Domsch 2009-05-14 00:23:52 UTC

Not sure this is still a problem; the thread jumped to email, where connectivity to the noted mirror was successful.

Comment 7 Matt Domsch 2009-05-19 15:26:37 UTC

with no follow-up, closing.