Bug #80321 Online YUM repository is not working
Submitted: 9 Feb 2016 15:49 Modified: 11 Feb 2016 8:20
Reporter: Daniel Holmes Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version: OS:Linux (RHEL)
Assigned to: CPU Architecture:Any
Tags: installation, yum

[9 Feb 2016 15:49] Daniel Holmes
Description:
Attempting to yum install MySql Community 5.6 version from http://repo.mysql.com/ I get this error as on Monday 2/8.  This was working up until the prior Friday.

http://repo.mysql.com/yum/mysql-5.6-community/el/7/x86_64/repodata/24cec160da485ad6878b6dc...: 
[Errno 14] HTTP Error 404 - Not Found--:--:-- ETA Trying other mirror.

It seems there is something not correct about the createrepo as something in the repomd.xml is refering to a sqllite file that does no exist in the repo.

This is the publically available repository for MySQL

How to repeat:
Configure YUM to the appropriate repo for RHEL 7.  Attempt to yum install mysql-community-server
[9 Feb 2016 18:55] Terje Røsten
Hi!

I am not able to reproduce:

$ wget http://repo.mysql.com/yum/mysql-5.6-community/el/7/x86_64/repodata/24cec160da485ad6878b6dc...

--2016-02-09 19:52:24--  http://repo.mysql.com/yum/mysql-5.6-community/el/7/x86_64/repodata/24cec160da485ad6878b6dc...
Resolving repo.mysql.com (repo.mysql.com)... 2.22.2.90
Connecting to repo.mysql.com (repo.mysql.com)|2.22.2.90|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 118038 (115K) [application/x-bzip]
Saving to: '24cec160da485ad6878b6dccee1d0dc3a591400a-primary.sqlite.bz2'

24cec160da485ad6878b6dccee1d 100%[===============================================>] 115.27K  --.-KB/s   in 0.03s  

2016-02-09 19:52:24 (3.60 MB/s) - '24cec160da485ad6878b6dccee1d0dc3a591400a-primary.sqlite.bz2' saved [118038/118038]

Might be problem with the CDN network.

Can you verify on your side with wget or curl?
[9 Feb 2016 19:40] Daniel Holmes
I am seeing the file now in the directory and can curl it.  It was not present earlier.  This could be a CDN update issue of the repomd.xml occuring ahead of the other sqllite files.  I'm guessing that the CDN update is not appearing transactional in that way?

Any other considerations we should be aware of here?  Are there update windows that are scheduled where this may generally happen or is this an unpredictable type of blip?

Thanks for looking into.
[11 Feb 2016 8:20] Terje Røsten
Hi Daniel,

nice to hear is works now.

I don't know the exact details of how the CDN update, however we have
seen similar problems in the past, aftersome time things seems to get 
into sync.

I am closing this report for now.

Thanks again for using MySQL Repos!