When a host in IAD2 does a mirrormanager query - e.g. https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-31&arch=x86_64 - the first result should always be the internal mirror dl.iad2.fedoraproject.org . However, if the request is served by proxy01 , often the list does not include the internal mirror at all (i.e. it responds as if the request had come from outside IAD2). When hitting proxy01, this happens about half the time. If the request hits one of the other proxy servers, it works fine.
We took proxy01 out of the DNS rotation for mirrors.fp.o to avoid this problem, but that was just a workaround, when we have time we should figure out why it's happening, fix it, and put it back in the rotation.
This is fixed by https://pagure.io/fedora-infra/ansible/pull-request/132
I fixed this when I was looking at #9028 but I just verified by explicitly connecting to the third mirrorlist server on proxy01 and that still has really old data.
from the batcave:
curl "https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-31&arch=x86_64" # repo = fedora-31 arch = x86_64 Using preferred netblock country = global http://dl.iad2.fedoraproject.org/pub/fedora/linux/releases/31/Everything/x86_64/os/ http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/x86_64/os/ ....
So this seems to be resolved.
Closing as such, feel free to re-open if you disagree :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
It think it was fixed on Sunday. The way to test is to go against each of the 4 proxies
curl -s -k -H 'Host: mirrors.fedoraproject.org' "https://proxy01.iad2.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64"| grep protocol= | grep -v rsync | head -n 1
several times as the old way would show dl.iad2 most of the time and then go off into lala land.
yeah, you have to try it multiple times. I'll ping if the problem shows up again.
Login to comment on this ticket.