Danny, I don't think it's your fault.
I am also getting the exact same error, for a configuration that always worked.
I haven't done a 'yum update' for a couple of weeks now.
Maybe the latest update to yum itself broke it.
As of now, I am waiting for a solution to pop up somewhere.
-nat
