Inactive/dead links in the EPEL 9 mirrorlist: #13405
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13405
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of request
Hello,
While checking the EPEL 9 mirrorlist:
https://mirrors.fedoraproject.org/mirrorlist?repo=epel-9&arch=x86_64
I found several mirrors that do not provide valid repository metadata (repodata/repomd.xml), causing failures in automated repo tools (e.g. Spacewalk/Uyuni sync).
Test output:
404 -> http://mirror.airenetworks.es/epel/9/Everything/x86_64/
000 -> https://mirror.netone.nl/other/epel/9/Everything/x86_64/
404 -> http://mirror.bahnhof.net/pub/epel/9/Everything/x86_64/
403 -> http://mirror.logol.ru/epel/9/Everything/x86_64/
404 -> https://mirror.centos.ikoula.com/9/Everything/x86_64/
These mirrors are still present in the official mirrorlist but fail to serve valid EPEL 9 repository metadata.
Expected:
All mirrors in the list should return valid repodata/repomd.xml (HTTP 200)
Actual:
Several mirrors return 404/403 or connection failure (000), breaking repository consumers.
Could you please review and remove or fix these mirrors in the EPEL 9 mirror pool?
Thanks.
So, none of those ones you list seem to be in the current list?
Note that mirrormanager uses a crawler to check if mirrors are up to date/have content. It is not instant, it takes a while to crawl all the sites and check all the various categories. I wonder if you checked at a time when a bunch of mirrors had dropped out.
Can you check again, as we think they've been removed from being served atm.
Note that there is a delay for the crawler, and it doesn't immediately remove mirrors so that temporary problems don't mean you have to add mirrors back.
I noticed that the 4xx mirrors are not showing up in metalink results, but they are showing up in mirrorlist results. Example: