Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 291269 [details] bug report
We should catch this in yum and pass up a yum error instead of the socket error.
Right, it probably just needs to use the "move to the next mirror" code path.
YUMBUGDAY
Fixed in git