Zypper doesn't show true mirror which has invalid content about zypper HOT 5 OPEN

Ping on this issue - we have seen multiple community reports of bad mirrors, but we can't diagnose which one is the issue without this feature. It's desperately needed because our community perception of opensuse as a distro is really suffering due to bad mirrors, and having tools so we can actually respond to these and provide updates will be so important.

from zypper.

@bzeller This has been an ongoing issue for our CI, and for helping users with mirror issues in the community. Could it be looked at please?

from zypper.

@Firstyear We talked about this in the meeting today, but as usual this is not as straigth forward as it seems to be. Especially when chunking comes into play, writing redirect information for every chunk would be horrible. Also if multiple servers for a chunk fail which one would be the one we blame for the error etc...

We already log all redirects into the logfiles though.

from zypper.

Well, the issue is currently we have no information at all though when an error occurs which means finding a broken mirror (which happens more commonly than wed like) is near impossible when users report issues in the community.

So we do need a way to filter-up the true source of the error to the caller. While it may be challenging it's important for us to help identify which mirrors are impact our users negatively (which in turn negatively affects our reputation as a distribution).

from zypper.

Some action on this would be nice - we can't troubleshoot why zypper commands are failing without the data about where it's pulling from.

Example error: https://github.com/kanidm/kanidm/actions/runs/5946810823/job/16127922982#step:5:216

from zypper.