Red Hat Bugzilla – Bug 728868
anaconda could not parse metalink during the net installation
Last modified: 2014-10-28 19:45:41 EDT
Description of problem:
In the process of install Fedora-16-Alpha-i386-netinst.iso in "Virtual Machine Manager 0.8.7", anaconda could not parse metalink, which would terminate the installation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora-16-Alpha-i386-netinst.iso in kvm like "Virtual Machine Manager 0.8.7"
2. Select the default options
Installation abort when anaconda try to retrieve repository metadata.
Installation completed successful.
It might be a problem of the default metalink url which was used by anaconda, the url is:
But by the result of accessing this url, we got this message:
"# repo = fedora-16-Alpha arch = i386 error: invalid repo or arch"
# following repositories are available:
# repo=fedora-16, arch=i386
so maybe the url should be https://mirrors.fedoraproject.org/metalink?repo=fedora-16&arch=i386 ?
Created attachment 517134 [details]
error log of anaconda 16.14.2
Created attachment 517135 [details]
Yeah, confirmed it. Shouldn't the repo link be fedora-16 instead of fedora-16-Alpha?
I believe this is the fault of the arguments passed to pungi (or lorax) when composing the installation ISO media. The version supplied, is expected to be an integer (16). However, the version supplied is a string (16-Alpha).
I believe we'll need either ...
1) A change in anaconda to strip out any non-integer elements in that string -- unsustainable patch imo ... string manip always fails
2) Respin the RC media using an 'integer' --version argument
3) Update MirrorManager to recognize the repo=fedora-16-Alpha
Adding dgilmore (rel-eng) since I believe options #2 and #3 fall into his realm.
as a workaround mirrormanager rediects have been put in place, however this really lies in anaconda land, the upgrade check strips off the -Alpha and -Beta and we should be doing the same here. we need to pass in 16-Alpha and 16-Beta for the version arguments to pungi to ensure that everything is named correctly.
(In reply to comment #5)
> as a workaround mirrormanager rediects have been put in place, however this
> really lies in anaconda land, the upgrade check strips off the -Alpha and -Beta
> and we should be doing the same here. we need to pass in 16-Alpha and 16-Beta
> for the version arguments to pungi to ensure that everything is named
I've confirmed the MirrorManager repo=fedora-16-Alpha redirect works. Will leave this issue open pending anaconda discussion on how to future-proof this defect.
If this is still reproducible (perhaps not what with the mirrormanager redirect, but maybe someone has a clever idea) can you test with:
(In reply to comment #7)
> If this is still reproducible (perhaps not what with the mirrormanager
> redirect, but maybe someone has a clever idea) can you test with:
Hrmm, yeah, I don't know how to retest this now that MirrorManager is in place. Maybe dgilmore can temporarily disable the MM changes?
Discussed in the 2011-08-08 Fedora QA meeting. The symptoms have been fixed but the original issue still remains. Accepted as NTH for Fedora 16 Alpha and re-proposed as Fedora 16 Blocker.
anaconda-16.14.3-1.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-16.14.3-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
According to the latest test results of anaconda 16.14.3, this problem has been fixed.
anaconda-16.14.4-1.fc16 has been submitted as an update for Fedora 16.
anaconda-16.14.5-1.fc16 has been submitted as an update for Fedora 16.
anaconda-16.14.6-1.fc16 has been submitted as an update for Fedora 16.
anaconda-16.14.6-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.