| Summary: | metalink xml is including ftp and rsync repo urls | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Lane <bcl> |
| Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | admiller, dennis, ffesti, firas.alkafri, jzeleny, kevin, matt_domsch, packaging-team-maint, satellitgo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-29 16:17:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
seen in f20 RC4 DVD x86_64 virtualbox install of both gnome and mate desktops. "unable to find metadata" I'm getting an FTP URL as the first entry, preventing me from setting up any repo via HTTP. Moving to mirrormanager gurus. Yeah, not sure whats going on here... I would expect the metalink to match the mirrorlist somewhat at least. Personally, I wonder if we should just drop all the ftp links at this point. Matt? Thoughts? Mirrors can provide content by multiple protocols. The /mirrorlist? endpoint reports only HTTP if the mirror provides both HTTP and FTP, or FTP if it doesn't serve HTTP. It doesn't include rsync. The /metalink? endpoint reports all protocols provided by the server, allowing the metalink consumer (in this case, yum) to determine which protocol it wants to use, by whatever method it wishes to decide this. It has done so since we introduced metalinks. This is consistent with the metalink definition and expected user experience - let the client decide what's best for itself, don't hard-code that server-side. The _ordering_ methodology of both mirrorlist/ and metalink/ is the same, it's only that metalinks include all provided protocols. Feel free to take this up with yum. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Things appear to be better, or at least different, with DNF. Haven't hit this one in a long time. |
After fixing up Anaconda to use the metalink url when generating the yum config people have notices installs taking an very long time to get started. In my case I notice that the metalink urls I get start with: <url protocol="ftp" type="ftp" location="US" preference="100" >ftp://linux.mirrors.es.net/fedora/linux/updates/20/x86_64/repodata/repomd.xml</url> <url protocol="http" type="http" location="US" preference="100" >http://linux.mirrors.es.net/fedora/updates/20/x86_64/repodata/repomd.xml</url> <url protocol="rsync" type="rsync" location="US" preference="100" >rsync://linux.mirrors.es.net/fedora/linux/updates/20/x86_64/repodata/repomd.xml</url> <url protocol="http" type="http" location="US" preference="99" mm0:private="True">http://download-i2.fedoraproject.org/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml</url> <url protocol="ftp" type="ftp" location="US" preference="98" >ftp://ftp.uci.edu/mirrors/fedora/linux/updates/20/x86_64/repodata/repomd.xml</url> <url protocol="http" type="http" location="US" preference="97" mm0:private="True">http://mirrors.zimcom.net/pub/fedora/linux/updates/20/x86_64/repodata/repomd.xml</url> ftp installs are going to be much slower than http, and I'm not even sure what it will do with an rsync url. If I look at the mirrorlist urls I see: # repo = fedora-20 arch = x86_64 Using Internet2 country = US country = CA http://mirrors.cat.pdx.edu/fedora/linux/development/20/x86_64/os/ http://mirrors.mit.edu/fedora/linux/development/20/x86_64/os/ http://mirror.cc.vt.edu/pub/fedora/linux/development/20/x86_64/os/ http://mirrors.zimcom.net/pub/fedora/linux/development/20/x86_64/os/ http://mirror.unl.edu/fedora/linux/development/20/x86_64/os/ http://mirror.pnl.gov/fedora/linux/development/20/x86_64/os/ http://mirror.umd.edu/fedora/linux/development/20/x86_64/os/ http://archive.linux.duke.edu/pub/fedora/linux/development/20/x86_64/os/ http://kdeforge2.unl.edu/mirrors/fedora/linux/development/20/x86_64/os/ http://fedora.osuosl.org/linux/development/20/x86_64/os/ http://mirror.ancl.hawaii.edu/linux/fedora/development/20/x86_64/os/ http://mirror.oss.ou.edu/fedora/development/20/x86_64/os/ ftp://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/development/20/x86_64/os/ In the whole list there are only 2 ftp urls. If I manually enter the mirrorlist url as the source for the install (and check the mirrorlist checkbox) the install proceeds at a reasonable rate. https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-20&arch=x86_64 If I leave the defaults, using metalink, it sometimes works slowly (5 minutes to populate the transaction set!) and sometimes not at all. I'm fairly sure the metalink xml should only be serving up http sources. Or at least a much higher ratio of http:ftp with the ftp ones further down the list like they were with the mirrorlist.