CentOS - Mar 2014 - The repodata directory is currently broken on several, if not all, mirrors for the 6.5 iso files

The repodata directory on all 6.5 isos that I have sampled have an issue where
the file names don't have extensions resulting in a yum repo error on
installation just after disk partitioning. This error prompts you with the
choice between either allowing you choose another repo or to exit the installer.
I remedied this issue with the following:

[root at testserv /root/test/centos]$ find repodata/ -type f -not -name
repomd.xml -exec sh -c 'mv {} -v $(grep -Po
"(?<=href=\")({}.*?)(?=\"/>)"
repodata/repomd.xml)' \;
?repodata/b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632?
->
?repodata/b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632-c6-x86_64-comps.xml?
?repodata/5af8199bd0ffb441c34ef946582d0d06c1ad770755e631690771e0bceb0ad222?
->
?repodata/5af8199bd0ffb441c34ef946582d0d06c1ad770755e631690771e0bceb0ad222-other.xml.gz?
?repodata/594d4bb4a79ed01d66635adbcf76c45ca4a85b30fc3e3c3c28316e64f0a83f21?
->
?repodata/594d4bb4a79ed01d66635adbcf76c45ca4a85b30fc3e3c3c28316e64f0a83f21-filelists.sqlite.bz2?
?repodata/6ac72f497df511cc2dc584eaa59779884fc572c1618e7c62dbd631ab8babf53d?
->
?repodata/6ac72f497df511cc2dc584eaa59779884fc572c1618e7c62dbd631ab8babf53d-filelists.xml.gz?
?repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c?
->
?repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c-primary.sqlite.bz2?
?repodata/ca525c73086186bfcb81ad9edd45796026dac7e4e50524e0f2daf901532aaf66?
->
?repodata/ca525c73086186bfcb81ad9edd45796026dac7e4e50524e0f2daf901532aaf66-c6-x86_64-comps.xml.gz?
?repodata/fdd542ef36b0cde54ee0521fae90b98911db06483163aa1c049995b6d109349b?
->
?repodata/fdd542ef36b0cde54ee0521fae90b98911db06483163aa1c049995b6d109349b-other.sqlite.bz2?
?repodata/495d3964f864fbab835ea1afb8a5272352cd12ded13d607205109fefaddd0ab6?
->
?repodata/495d3964f864fbab835ea1afb8a5272352cd12ded13d607205109fefaddd0ab6-primary.xml.gz?

The repomd.xml file has the correct names for the files, the files in this
directory just have the sha sums as their file names, not the full path name as
defined in the xml file. This results in yum breaking just after partitioning.
The only way I was able to get around this before modifying the iso file was to
follow the onscreen prompt and enter in a valid mirror as an HTTP/FTP host. This
issue is currently afflicting all variants of 6.5.

As of this writing the two test files I just confirmed have this issue are:

http://mirror.cisp.com/CentOS/6.5/isos/x86_64/CentOS-6.5-x86_64-minimal.iso
http://mirrors.bluehost.com/centos/6.5/isos/x86_64/CentOS-6.5-x86_64-minimal.iso

Last night I downloaded the minimal, livecd, livedvd and netinstall isos from
10+ mirrors. All of them triggered the error from the files not being named
correctly.

--Shields

On 03/29/2014 02:01 AM, jshields at hostgator.com wrote:
> The repodata directory on all 6.5 isos that I have sampled have an issue
where the file names don't have extensions resulting in a yum repo error on
installation just after disk partitioning. This error prompts you with the
choice between either allowing you choose another repo or to exit the installer.
[snip]
> The repomd.xml file has the correct names for the files, the files in this
directory just have the sha sums as their file names, not the full path name as
defined in the xml file. This results in yum breaking just after partitioning.
The only way I was able to get around this before modifying the iso file was to
follow the onscreen prompt and enter in a valid mirror as an HTTP/FTP host. This
issue is currently afflicting all variants of 6.5.
>
> As of this writing the two test files I just confirmed have this issue are:
>
> http://mirror.cisp.com/CentOS/6.5/isos/x86_64/CentOS-6.5-x86_64-minimal.iso
>
http://mirrors.bluehost.com/centos/6.5/isos/x86_64/CentOS-6.5-x86_64-minimal.iso
I downloaded the x86_64 minimal iso file from the bluehost.com and the 
kernel.org mirrors, and I'm not seeing what you're describing. Both have
the full pathnames in the repodata directory.

Do you have some unusual mount options that you're using?  I tested with 
a simple "mount -o ro,loop" invocation.

-Greg