One of the configured repositories failed (Unknown), 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. Disable the repository, 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 <repoid> 4. 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 compromise:
解决方法：
vi /etc/yum.repos.d/epel.repo 修改前 [epel] name=Extra Packages for Enterprise Linux 7 - $basearch baseurl=http://mirrors.cloud.aliyuncs.com/epel/7/$basearchfailovermethod=priority enabled=1gpgcheck=0 修改后 [epel] name=Extra Packages for Enterprise Linux 7 - $basearch #baseurl=http://mirrors.cloud.aliyuncs.com/epel/7/$basearchfailovermethod=priority enabled=0gpgcheck=0
原文地址：https://www.cnblogs.com/yunweiweb/p/11646960.html