I am coming across a broken mirror in my logs: Bytemark mirror
I contacted Bytemark who said I should use a different mirror as they do not actively maintain theirs.
Perhaps this should be removed from the active mirror list.
cc: @abompard
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
For the record, that's https://mirrormanager.fedoraproject.org/host/1174. I looked at their data in MirrorManager, and indeed their Fedora mirror is not available, but their EPEL mirror is working. As a result the host does not get disabled, since enabling/disabling is a host-level thing.
Maybe we could make that a category-level thing? What do you think @adrian ? (or am I missing something?)
In the meantime, can you reply to Bytemark and ask them to remove their "Fedora Linux" category in MirrorManager at https://mirrormanager.fedoraproject.org/host/1174 ? I could do it but it's always better if it's the actual mirror owner that does this sort of thing. In case they forgot, their FAS username is bytemarkmirrors (or patch0)
bytemarkmirrors
patch0
I sent a follow-up email as you suggested @abompard , I received no reply but the "Fedora Linux" category is now functional again, so maybe the right person saw it this time.
But on a wider point, disabling hosts based on a category-level does seem sensible.
@triatic might you file a upstream ticket on mirrormanager to add that?
https://github.com/fedora-infra/mirrormanager2/issues/new/choose
or if you prefer, I or @abompard can
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Sure, go ahead! I'm pretty new to Fedora so I'm sure you could word the feature request better than me.
Filed: https://github.com/fedora-infra/mirrormanager2/issues/376
Log in to comment on this ticket.