the epel repo uses "basearch" in the mirror string
so 32 bit and 64 bit use the same file

odd
you uninstalled epel BUT it is still installed
manually remove them

i am guessing you might have 10 or 20 different epel.reop files in your " /etc/yum.repos.d " folder


because once you uninstall it
it should NOT still be installed

and post the output of this command

Dear John,
Ok I tried the command also the same as below.

But below are the files for in /etc/yum.repos.d

Dear John,
Anything else that I must provide you please do let me know? Thank you.

then REREAD post #16
to repeat and i QUOTE

you DID uninstall ??? BUT you did not .
the output you posted above SHOWS you did not uninstall the epel repo

Dear John,
Ok I went into the folder and just run the rm command for all those epel files and I am able to run yum update now. By just rm the files is considered uninstall is it? Thank you.

no rm dose not uninstall

i am only guessing but you might have had a few different copies of the epel repo
or
you never unistalled all the different epel.rpeo rpms

Dear John,
So I guess I must run yum remove the name of epel files in the /etc/yum.repos.d? Thank you for the help and appreciate most.

Hi,
I just found this googling the same problem. The difference is that I just built 3 machines with identical harware and identical setup, but one of them gave the error:

on yum update.

After trying to get the metadata directly with :

I got the error :

Which lead to the root of the real problem...
On Server 1 (working):

On Server 3 (not working):
So fixing the date, fixed the 'not yet valid certificate' error (which yum doesn't tell you about) and now yum updates.

Regards,
Chris.

Why do it that way? The documentation and nobody here suggested you should.


Check the official EPEL-release package and you'll find the URIs are HTTP, not HTTPS?


So how did you "fix" that then?

* If you did it by setting "sslverify=0" in the repo file then why use SSL in the first place?

I came here from google from having the same problem. I read this thread and it wasn't solved.
My process was :

rpm -Uvh http://mirrors.coreix.net/fedora-epe...6-7.noarch.rpm
yum update
and then got:
Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again

running wget generally gives you a bit more information about the problem when it comes to eliminating download errors (not to install / fix / update anything).

Anyway, the point was that the date was wrong on the server, which is what was causing the error (for me anyway) and maybe it would be helpful for other people.

...to answer my own question apparently the new epel-release repo file does default to using HTTPS.

I had the same problem. I had installed the epel rpm using yum. After I removed it using yum erase and reinstalled using rpm, the problem went away.