Estou usando o vagrant para inicializar uma VM do centOS 7.0. Meu provedor está tentando configurar o EPEL 7 via
yum install epel-release -y
e, em seguida, tentando instalar o ansible via
yum install ansible -y
Ele instala o epel-release com sucesso, mas ao tentar executar outros comandos do yum, eu começo a ver:
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:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
Após algumas etapas de depuração:
yum --disablerepo="epel" check-update
Funcionou bem. Então eu tentei
URLGRABBER_DEBUG=1 yum check-update 2> debug.log
No final do debug.log, vejo o erro real:
< HTTP/1.1 200 Connection established
<
2015-03-30 20:54:18,080 header ended:
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5990 (PR_IO_TIMEOUT_ERROR)
* I/O operation timed out
* Closing connection 10
2015-03-30 20:54:48,110 exception: [Errno 14] curl#35 - "I/O operation timed out"
2015-03-30 20:54:48,110 retrycode (14) not in list [-1, 2, 4, 5, 6, 7], re-raising
Estou um pouco perdido sobre como corrigir esse problema. Note que, às vezes, isso simplesmente funciona, mas, em 95% do tempo, a tentativa de obter metadados de repo do EPEL falha. Isso é um problema no meu fim? Eu estou roteando através de um proxy, mas parece que o proxy está funcionando bem. Eu acho que a parte mais confusa é que funciona muito raramente.
No nosso caso, era um problema de firewall ... estávamos permitindo o acesso http (porta 80) de saída do host, mas não o https (443). Os repositórios regulares são acessados por meio do primeiro, mas as reposições EPEL são feitas por meio do segundo. Então, sem o EPEL no loop a 'yum update' (ou qualquer outra coisa) estava funcionando bem, mas com EPEL, estava bombardeando,
== > Um dos repositórios configurados falhou (Desconhecido) ...
Pffft. Agora nós sabemos!
Esse problema ocorre quando você está solicitando o yum para obter o repo sem conexão com a internet. você instalou o lançamento da epel. mas não há conexão com a internet para instalar o ansible.
Eu comentei o meu resolve.conf como abaixo e tentei. Eu tenho o mesmo erro.
[root@controller yum.repos.d]# cat /etc/resolv.conf
# Generated by NetworkManager
#nameserver 8.8.8.8
[root@controller yum.repos.d]#
[root@controller yum.repos.d]# yum install ansible -y
Loaded plugins: fastestmirror
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:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
Este é o comportamento normal da última versão do Centos 7.
Se você tiver problemas para acessar a Internet da sua VM, verifique este link .