[SERVER-20095] Redhat repository broken - Metadata file does not match checksum Created: 24/Aug/15  Updated: 25/Aug/15  Resolved: 24/Aug/15

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andy Lee Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-20087 Debian repository broken - Hash Sum m... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Fresh install of CentOS 7.

$ cat /etc/yum.repos.d/mongodb-org-3.0.repo
 
[mongodb-org-3.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/
gpgcheck=0
 
$ yum search mongo

Participants:

 Description   

Similar problem to SERVER-20087.

mongodb-org-3.0/primary                                                                                      | 8.9 kB  00:00:00     
https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
 
 
 One of the configured repositories failed (MongoDB Repository),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:
 
     1. Contact the upstream for the repository and get them to fix the problem.
 
     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).
 
     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:
 
            yum-config-manager --disable mongodb-org-3.0
 
     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:
 
            yum-config-manager --save --setopt=mongodb-org-3.0.skip_if_unavailable=true



 Comments   
Comment by Ernie Hershey [ 24/Aug/15 ]

No problem. Thanks for the bug report!

You will probably get a better response and more helpful eyes on problems like this in the future if you email the google group, which is more for usage and operational problems as opposed to the SERVER jira which is more for bugs in MongoDB.

https://groups.google.com/forum/?#!forum/mongodb-user

Comment by Andy Lee [ 24/Aug/15 ]

Everything is fine now. Thank you for looking into it.

Comment by Ernie Hershey [ 24/Aug/15 ]

alee@intellisurvey.com - Can you try again and let me know if you get the same error?

I apologize for the problem. We've been having trouble with the CDN cache in front of our packaging repositories. We published new packages this morning. You may have caught a partially updated edge node that has up to date checksums and stale metadata files, or vice versa. I just tried the same scenario in CentOS 7 and was able to search for and install mongodb packages.

Generated at Thu Feb 08 03:53:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.