MirrorManager tripped over the EPEL 9 next directory structure:
# pwd /srv/pub/epel/testing/next/9 # find . -name repodata ./Everything/x86_64/debug/repodata ./Everything/x86_64/repodata ./Everything/aarch64/debug/repodata ./Everything/aarch64/repodata ./Everything/ppc64le/Packages/debug/repodata ./Everything/ppc64le/Packages/os/repodata ./Everything/ppc64le/drpms/debug/repodata ./Everything/ppc64le/drpms/os/repodata ./Everything/ppc64le/debug/repodata ./Everything/ppc64le/repodata ./Everything/s390x/debug/repodata ./Everything/s390x/repodata ./Everything/source/tree/repodata
For ppc64le there are two locations for the non-debug and debug repository. That breaks the primary mirror scanner.
ppc64le
CC: @mohanboddu
Same problem for the non-testing part of the tree.
Oh, and a repodata directory without repomd.xml is also problematic and breaks the detection.
repodata
@carlgeorge This is probably something you can help with.
This looks like it is happening in the epel-9 compose. The timestamps for these files are incredibly bad
$ ls -l total 12 drwxr-xr-x. 2 263 263 4096 2018-02-20 19:13 Packages/ drwxr-xr-x. 2 263 263 4096 2018-02-20 19:13 drpms/ drwxr-xr-x. 2 263 263 4096 2018-02-20 19:13 repodata/
Something has created timestamps 2 years in the past for everything in 9-next.
There hasn't been an epel9 or epel9-next compose yet. I believe @mohanboddu created that repodata manually to allow new-updates-sync (bodhi2/backend) to run.
https://pagure.io/fedora-infrastructure/issue/10257#comment-756693 and https://pagure.io/fedora-infrastructure/issue/10257#comment-756694
Closing this ticket.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
epel/next/9/Everything/s390x/debug/repodata/ still has no repomd.xml (testing also).
Metadata Update from @adrian: - Issue status updated to: Open (was: Closed)
Metadata Update from @mohanboddu: - Issue assigned to mohanboddu - Issue tagged with: medium-gain, medium-trouble, ops
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
I went ahead and fixed that last repodata dir. Let us know if you still see any issues...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.