[SERVER-26564] Yum errors out when trying to install mongo-org on RHEL 7.2 Created: 10/Oct/16 Updated: 19/Nov/16 Resolved: 14/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jared Bristow | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Evergreen 2016-10-31 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Here's the output from the command line: =================================================================================================================================================================================== Transaction Summary Total size: 59 M Error downloading packages: I'm not having issues on other OSes (CentOS 7, CentOS 6, RHEL 6). Just RHEL7. I can download the RPM with my browser just fine, so I think the issue is with a GPG key The URL for the mongo repo is: On my redhat server, the $releasever variable resolves to "7Server". Browsing to "https://repo.mongodb.org/yum/redhat/", and can see that "7" is an available option. I changed the $releasever variable to that in my mongo repo file, and then run the yum install. It asks me to accept a key, and then the install works. Here's the request to accept the key: Because I was suspicious about the key being the issue, I tried removing the mongodb-org, switching my repo back to using $relesasever, and then installing mongodb-org again. This time it worked. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 14/Oct/16 ] |
|
Sorry for not updating this ticket sooner, I've been tracking this repair work in other tickets and have neglected to update this ticket. There was an underlying problem in our package publishing jobs that lead to occasionally uploading data that was not properly signed, which should now be fixed for all branches. I've attempted to clean up the existing repositories but there are some reports that I've not been able to observe about unsigned packages in this repository. I've not been able to reproduce these reports at this point, and they may be due to caching in the CDN, but I will continue to look into this today. I'm glad that the /7/ repository gave you a quick work around to this issue, and sorry for any inconvenience or confusion that this has caused. Regards, |
| Comment by Githook User [ 14/Oct/16 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 14/Oct/16 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: (cherry picked from commit 4b06a21895f292f45f58659a2e674d4e80e65614) |
| Comment by Githook User [ 14/Oct/16 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |