#7370 Getting 404 from f29 updates repo on ppc64le, is updates mirror out of sync?
Closed: Fixed Opened by sinnykumari.

Trying to install a package on f29 ppc64le box gives 404 while fetching information from fedora-updates repo

# dnf install  -v ShellCheck
Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade
DNF version: 4.0.4
cachedir: /var/cache/dnf
repo: downloading from remote: updates
error: Status code: 404 for https://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml (https://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml).
error: Status code: 404 for http://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml (http://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml).
Fedora 29 - ppc64le - Updates                                                                                              59  B/s | 280  B     00:04    
Cannot download 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f29&arch=ppc64le': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried.
Error: Failed to synchronize cache for repo 'updates'

Note: It was working fine till yesterday


Odd. Are you sure the fedora-updates.repo hasn't been changed?

There were not any bodhi or updates-sync changes recently that I can think of.

@adrian can you see whats going on here?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Odd. Are you sure the fedora-updates.repo hasn't been changed?

No, I didn't change content in fedora-updates.repo . Should be easily reproducible if one has F29 ppc64le vm access.
* Run sudo dnf clean all and then install anything sudo dnf install Shellcheck

It seems that the updates-modular is failing also see https://github.com/fedora-cloud/docker-brew-fedora/issues/61

seems mirrormanager returns the wrong URLs

[dan@localhost ~]$ curl 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f29&arch=ppc64le'
<?xml version="1.0" encoding="utf-8"?>
<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Wed, 14 Nov 2018 09:53:32 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">
  <files>
    <file name="repomd.xml">
      <mm0:timestamp>1519154018</mm0:timestamp>
      <size>3068</size>
      <verification>
        <hash type="md5">a9918dad730aec1c339f9fce05cb01d3</hash>
        <hash type="sha1">13be7bda8c2da37a075dae3f40bbbdfe5845c592</hash>
        <hash type="sha256">94719c762e3e096a2c330d2292a9e76a8b935015a290d20fdbd7a2b920a09a5b</hash>
        <hash type="sha512">c241e00f6839a095c5c16df5e7305a9157a8d418f38547edc642378c6b3f53601cf0ee81034382aa1baa56d354fa5a2d9e67fc8b29523097e86f11a5b85c622b</hash>
      </verification>
      <resources maxconnections="1">
        <url protocol="http" type="http" location="US" preference="100" >http://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml</url>
        <url protocol="https" type="https" location="US" preference="100" >https://dl.fedoraproject.org/pub/fedora-secondary/updates/29/Everything/ppc64le/Packages/os/repodata/repomd.xml</url>
      </resources>
    </file>
  </files>
</metalink>

So MirrorManager is pointing to a directory which does not exist. This seems to be the usual problem. A repository was published, MirrorManager picked it up, a while later the paths were changed. MirrorManager cannot handle paths that are changing.

Oh, this was actually predicted here: https://pagure.io/releng/issue/7844

I deleted the wrong entries from the database and MirrorManager already picked up the new repositories. It should be fixed soon (not more than 2 hours).

Please re-open if this is not fixed in 2 hours.

Metadata Update from @adrian:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thanks @adrian ! Got fixed now.

Metadata