Bug 373471 - yum secretly adds repo urls which aren't under /etc/yum.repos.d
Summary: yum secretly adds repo urls which aren't under /etc/yum.repos.d
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 8
Hardware: All
OS: Linux
high
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-09 19:17 UTC by Don Zickus
Modified: 2014-01-21 23:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-12 15:31:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Don Zickus 2007-11-09 19:17:00 UTC
Description of problem:
So I did a fresh install of F8 on my laptop from qafiler (as pointed out by
Warren).  I booted my machine, pirut started and updated my box, and I shutdown
the machine.  

I brought the machine home, fired off a yum install <foo> and it failed to find
download.boston.redhat.com.  Now nowhere did I ever enter the address during my
install.  Even a 'grep -r boston /etc/*' yielded nothing (except dhcpclient).

How the hell??!!  Anyway a 'yum install --disablerepo=* --enablerepo=f* <foo>'
works around the issue.  I have no idea why.


Version-Release number of selected component (if applicable):
fresh install of F8

How reproducible:
everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Seth Vidal 2007-11-09 19:24:02 UTC
Do you have any:
mirrorlist= lines?

the mirrorlists are handed back based on the best ones for your ip.

this is not a bug

Comment 2 Don Zickus 2007-11-09 20:06:06 UTC
that's bs.

I changed IP addresses as I went from the company network to my home network.

If yum can't handle that through mirrorlists than that's a bug in of itself.

Regardless, I do have mirrorlist= lines (but none of the contain *boston*

ps sorry for being grumpy.  just sucks to install a laptop and have so many
issues.  ;-)

Comment 3 Seth Vidal 2007-11-09 20:13:19 UTC
you changed networks but the mirrorlists were still cached. So yum used the
within-cache-expiration mirrorlists rather than grab new ones. Your old ones
were for the boston office's vpn only.

There's the problem.

yum can handle changing networks fine - but it has no way of knowing that your
successfully cached mirrorlist is incorrect on this network.



Comment 4 Don Zickus 2007-11-09 20:20:06 UTC
should it cache the ip address with the mirrorlist? that way if the ip address
changes it can invalidate the mirrorlists?

Comment 5 Seth Vidal 2008-03-12 15:31:01 UTC
No, Set your mirrorlist_expire variable to a smaller number.

Comment 6 Don Zickus 2008-03-12 16:05:52 UTC
I assume 'mirrorlist_expire' is supposed to be in /etc/yum.conf?  If it is, I
don't have a variable nor value to set smaller.

Also any way to make this problem more obvious to the casual user so they don't
scratch their head and file bugzillas? :-)

Comment 7 Seth Vidal 2008-03-12 16:14:35 UTC
man yum.conf

it's in there on mine.

The casual user doesn't have a separate mirror at work than the ones at home.



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