Red Hat Bugzilla – Bug 488564
repo --mirrorlist in kickstart is broken
Last modified: 2009-04-06 10:33:54 EDT
Created attachment 334054 [details]
Description of problem:
When repo --mirrorlist=... is specified in kickstart, installation dies.
Version-Release number of selected component (if applicable):
Everything that comes with F10 (anaconda 220.127.116.11)
Every time, just use the kickstart file provided
Steps to Reproduce:
1. network install by kickstart
anaconda 18.104.22.168 exception report
Traceback (most recent call first):
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 574, in _replace_and_check_url
if url[-1] != '/':
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 538, in _baseurlSetup
self.baseurl = self._replace_and_check_url(self.baseurl)
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 593, in _geturls
(see full version attached)
Expected to see mirrorlist option working.
It seems that if addition repositories are specified with repo, but baseurl is not specified (instead mirrorlist is used), parsing of baseurl fails and everything dies.
I'm seeing the same problem in F10 as well, with the same traceback. The offending lines for me are:
repo --name=rpmfusion-free --mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-10&arch=i386
repo --name=rpmfusion-nonfree --mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-10&arch=i386
repo --name=rpmfusion-free-updates --mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-10&arch=i386
repo --name=rpmfusion-nonfree-updates --mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-10&arch=i386
repo --name=everything --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-10&arch=i386
repo --name=fedora-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f10&arch=i386
A quick test with these same lines in F11 Beta shows this is no longer a problem. Can you please also test and verify that you are not seeing this problem anymore? Thanks.
It looks like i386 images failed to build today, but everything looks like it worked using the images I had from March 27th.
Okay, thanks for testing.