Description of problem:
Repeat of bug https://bugzilla.redhat.com/show_bug.cgi?id=1846561
Unsure if I should comment or open new bug
Since today, we are getting a very high volume of failures from the epel 7 repo.
http://mirrors.chroot.ro/fedora/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel
Trying other mirror.
We get about 100 of these types (different mirrors obviously) and then an eventual failure:
https://mirror.linux-ia64.org/epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.linux-ia64.org/epel/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=epel ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable epel
subscription-manager repos --disable=epel
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
yum-config-manager --save --setopt=epel.skip_if_unavailable=true
I am having trouble understanding how this is a problem with the python2-requests package, or indeed with any package in the distribution. It seems to me that you need to raise your issue on an appropriate mailing list, or in a ticket filed with Fedora Release Engineering.