Bug 487925 - anaconda is unable to fetch repomd.xml
Summary: anaconda is unable to fetch repomd.xml
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11Beta, F11BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2009-03-01 14:04 UTC by Julian Sikorski
Modified: 2009-03-07 12:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-07 12:25:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda log (12.45 KB, text/plain)
2009-03-02 20:42 UTC, Jeffrey C. Ollie
no flags Details
syslog from failed install (44.43 KB, text/plain)
2009-03-02 20:43 UTC, Jeffrey C. Ollie
no flags Details

Description Julian Sikorski 2009-03-01 14:04:32 UTC
Description of problem:
I suspect this might have something to do with the fact that sha256 is used now. It tries to download the file 10 times, and then says it was impossible to fetch the metadata.

Version-Release number of selected component (if applicable):
11.5.0.23

How reproducible:
always

Steps to Reproduce:
1. Try to install rawhide
2. Wait until after partition creation
3. Observe the failure
  
Actual results:
Failed to get repomd.xml from mirror 1/1, or the downloaded file is corrupt.

Expected results:
Rawhide installs without problems.

Additional info:
I tried a few mirrors, including download.fedora.redhat.com. This installation was attempted in a kvm machine. I switched to vt2 and wget'd the said file, wich worked. This eliminates networking issues, I guess.

Comment 1 Julian Sikorski 2009-03-01 14:14:21 UTC
Here is the line I used:
virt-install --os-type=linux --location=http://download.fedora.redhat.com/pub/fedora/linux/development/x86_64/os/ --name=rawhide-x86_64 --vcpus=1 --file=/ --accelerate --nonsparse --ram=512 --file-size=10 --arch=x86_64 --hvm --sound --os-variant=fedora11

Comment 2 Julian Sikorski 2009-03-01 14:15:45 UTC
erm, make that --file=/var/lib/libvirt/images/rawhide-x86_64.img

Comment 3 Jeffrey C. Ollie 2009-03-02 20:31:32 UTC
I'm seeing the same thing, except that I'm installing via cobbler (PXE boot and http url).  Switching to the shell on Alt-F2 I'm able to use wget to download the repomd.xml manually, so it does not appear to be a network problem (esp since this is a PXE boot, and Anaconda is able to download the install.img without problems.

Comment 4 Jeffrey C. Ollie 2009-03-02 20:42:53 UTC
Created attachment 333784 [details]
anaconda log

Comment 5 Jeffrey C. Ollie 2009-03-02 20:43:30 UTC
Created attachment 333785 [details]
syslog from failed install

Comment 6 Jeffrey C. Ollie 2009-03-02 20:45:19 UTC
Actually, from looking at the logs from the webserver that hosts my local repo, Anaconda never even attempts to contact the webserver for repomd.xml.  I've attached the /tmp/anaconda.log and /tmp/syslog from the latest failed attempt.

Comment 7 Jeffrey C. Ollie 2009-03-02 20:56:11 UTC
Another thing that I noticed is that the retrieval of the install.img is much slower under F11 than F10.

Comment 8 Julian Sikorski 2009-03-03 17:09:57 UTC
Today's rawhide isn't any better, the problem is still present.

Comment 9 Chris Lumens 2009-03-05 01:38:42 UTC
Could you check the repo config files in /etc/anaconda.repos.d and see whether they specify metalink=, with baseurl= and mirrorlist= commented out?  I believe that's the problem here, and I've been waiting on a new yum (which should have been built earlier today) to handle these URLs a little differently before making changes to anaconda.

Comment 10 Julian Sikorski 2009-03-05 18:23:49 UTC
Yeah, that's it. metalink present, basearch and mirrorlist commented out. So, will things work with yesterday's yum, or are anaconda changes needed as well?

Comment 11 Julian Sikorski 2009-03-07 11:13:50 UTC
This seems to be fixed with yesterday's rawhide, although I believe it was the fedora-release workaround which did the trick.


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