#4839 yum metadata for secondary arch does not match
Closed: Fixed None Opened 4 years ago by msuchy.

On PPC64LE architecture:

{{{
[root@rh-power-vm26 ~]# LC_ALL=C yum-deprecated upgrade
Yum command has been deprecated, use dnf instead.
See 'man dnf' and 'man yum2dnf' for more information.

fedora/22/ppc64le/metalink | 3.0 kB 00:00:00
updates/22/ppc64le/metalink | 1.8 kB 00:00:00
updates | 3.7 kB 00:00:00
http://fr2.rpmfind.net/linux/fedora-secondary/updates/22/ppc64le/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates
Trying other mirror.
updates | 3.7 kB 00:00:00
http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/22/ppc64le/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates
Trying other mirror.
updates | 3.7 kB 00:00:00
http://dl.fedoraproject.org/pub/fedora-secondary/updates/22/ppc64le/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates
Trying other mirror.

One of the configured repositories failed (Fedora 22 - ppc64le - Updates),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:

        yum-config-manager --disable updates

 4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=updates.skip_if_unavailable=true

failure: repodata/repomd.xml from updates: [Errno 256] No more mirrors to try.
}}}

It currently block Copr builds for PPC64LE architecture.


Thanks for the report. The process which analyses the master mirror failed for the last few days. I think I have a fix and I am currently running a manual scan of the master mirror. If this works it should make its way to the mirrorlist servers in the next few hours.

it affects all secondary arches it seems

Still working on the real fix but as the scanning of the tree takes rather long this takes some time. To get the metalinks in a working state I have manually updated the secondary arches repomd.xml files in the MirrorManager database until the actual tool is fixed.

Fix has been released in MirrorManager2 0.4.1 and deployed in production.

Login to comment on this ticket.

Metadata