MySQL Bugs: #83271: Partial mirrors of yum repository now fail

Bug #83271	Partial mirrors of yum repository now fail
Submitted:	5 Oct 2016 14:19	Modified:	1 Feb 2017 14:15
Reporter:	Ray Shaw	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Package Repos	Severity:	S3 (Non-critical)
Version:	5.6.x	OS:	Red Hat (6 and 7)
Assigned to:		CPU Architecture:	Any

Description:
I have a requirement for a local, partial mirror of the MySQL yum repository (specifically, only the RPM packages for 5.6). This is used as part of the process to update systems that are not connected to the Internet (and cannot be).

I previously used the following commands to maintain this mirror:

echo "mirror --only-missing --no-empty-dirs -I *.rpm" | lftp http://repo.mysql.com/yum/mysql-5.6-community/el/6/x86_64/
echo "mirror --only-missing --no-empty-dirs -I *.rpm" | lftp http://repo.mysql.com/yum/mysql-5.6-community/el/7/x86_64/

This was working as recently as July 2016, and run daily. At some point between then and now, it stopped working; it just stalls forever and never manages to download anything. I noticed due to the systems not being updated with 5.6.33.

Since I can still access the repo just fine using a browser from the same system where lftp fails, I assume there has been some configuration change, intentional or not, that's preventing this from working. I attempted to use a mirror site, but it seems the MySQL mirrors are not mirrors of the yum repository, merely the download site, so that's not particularly useful to me.

Please advise on how to proceed. My two requirements are:

- Need a local mirror of the MySQL yum repository
- Need to only mirror part of the repo due to limited disk space

Sorry if this is not the correct means of reporting this issue, but I couldn't find another way to do it (everything else seems to lead to sales).

How to repeat:
Run this on Linux:

echo "mirror --only-missing --no-empty-dirs -I *.rpm" | lftp http://repo.mysql.com/yum/mysql-5.6-community/el/6/x86_64/

Hello Ray Shaw,

Thank you for the report.

Thanks,
Umesh

Posted by developer:
 
Acknowledged.

Posted by developer:
 
This appears to be caused by the global content delivery network that Oracle uses for download mirroring taking time to sync up. This would cause intermittent issues of the kind observed.