Description of problem: Yum reports ovirt-4.2-epel is corrupted. Inclusion of this repo results in yum reporting: file is encrypted or is not a database This obviously prevents host installations. Version-Release number of selected component (if applicable): 4.2.3.5-1.el7.centos How reproducible: Always since about an hour ago. Steps to Reproduce: 1. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm 2. yum update Actual results: ```[root@vm1 yum.repos.d]# yum update Loaded plugins: fastestmirror, versionlock Determining fastest mirrors ovirt-4.2-epel/x86_64/metalink | 5.5 kB 00:00:00 * base: centos.mirror.vexxhost.com * extras: centos.mirror.vexxhost.com * ovirt-4.2: mirrors.rit.edu * ovirt-4.2-epel: ewr.edge.kernel.org * updates: centos.mirror.vexxhost.com Webmin | 1.0 kB 00:00:00 base | 3.6 kB 00:00:00 centos-sclo-rh-release | 3.0 kB 00:00:00 extras | 3.4 kB 00:00:00 ovirt-4.2 | 3.0 kB 00:00:00 ovirt-4.2-centos-gluster312 | 2.9 kB 00:00:00 ovirt-4.2-centos-opstools | 2.9 kB 00:00:00 ovirt-4.2-centos-ovirt42 | 2.9 kB 00:00:00 ovirt-4.2-centos-qemu-ev | 2.9 kB 00:00:00 ovirt-4.2-epel | 4.7 kB 00:00:00 ovirt-4.2-virtio-win-latest | 3.0 kB 00:00:00 updates | 3.4 kB 00:00:00 (1/14): base/7/x86_64/group_gz | 166 kB 00:00:00 (2/14): extras/7/x86_64/primary_db | 104 kB 00:00:00 (3/14): ovirt-4.2/7/primary_db | 483 kB 00:00:00 (4/14): base/7/x86_64/primary_db | 5.9 MB 00:00:00 (5/14): ovirt-4.2-centos-opstools/x86_64/primary_db | 196 kB 00:00:00 (6/14): ovirt-4.2-centos-gluster312/x86_64/primary_db | 102 kB 00:00:00 (7/14): centos-sclo-rh-release/x86_64/primary_db | 3.2 MB 00:00:00 (8/14): ovirt-4.2-centos-ovirt42/x86_64/primary_db | 119 kB 00:00:00 ovirt-4.2-epel/x86_64/primary_ FAILED http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/65e078711712530080b8c3cc68254df2c2394a17477f8718d7090bbfa990be1e-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found0.0 B/s | 8.3 MB --:--:-- ETA Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. (9/14): ovirt-4.2-centos-qemu-ev/x86_64/primary_db | 37 kB 00:00:00 (10/14): ovirt-4.2-epel/x86_64/group_gz | 84 kB 00:00:00 (11/14): ovirt-4.2-epel/x86_64/updateinfo | 921 kB 00:00:00 (12/14): updates/7/x86_64/primary_db | 1.0 MB 00:00:00 (13/14): ovirt-4.2-epel/x86_64/primary_db | 1.6 MB 00:00:00 (14/14): ovirt-4.2-virtio-win-latest/primary_db | 6.4 kB 00:00:00 Webmin/primary | 15 kB 00:00:00 Webmin 116/116 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. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 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 <repoid> or subscription-manager repos --disable=<repoid> 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 compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true file is encrypted or is not a database ``` Expected results: Successful yum update. Additional info: Started happening an hour ago. Tried clearing the cache via rm -rf /var/cache/yum to try multiple mirrors. Tried about 7 times. Same error always.
We have no control on EPEL YUM repositories. I reported this to EPEL developers at https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/WC7T2SOTX2LDC2X3FKSBLZQR3LB2PUDP/ Closing upstream.