[SERVER-31698] Packages cannot be authenticated — revisited Created: 24/Oct/17 Updated: 15/Oct/18 Resolved: 27/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 3.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Newton | Assignee: | Zakhar Kleyman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | On a brand new server running Ubuntu 16.04.3, I follow the steps to install MongoDB Community Edition, as described here. After executing the line `sudo apt-get install mongodb-org`, I get this warning:
I tried the steps proposed by Brian Samek for the earlier bug, updating them to the current version:
My complete terminal session is shown below. $ sudo find / -name "mongo*" |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
This bug looks very similar to an earlier one which was apparently resolved: The MongoDB 3.6 Release Signing Key appears not to be recognized: mongodb packages cannot be authenticated. |
| Comments |
| Comment by Ramon Fernandez Marina [ 06/Jun/18 ] | |||||||||||||||||||||||||||||
|
Hi jgoeglein; this behavior is expected:
Glad to hear you were able to sort this out – and thanks for posting detailed instructions on how to address this for everyone else that runs into this issue. Regards, | |||||||||||||||||||||||||||||
| Comment by Jesse Goeglein [ 06/Jun/18 ] | |||||||||||||||||||||||||||||
|
Hello Zakhar, Sorry to resurrect a closed ticket, but it looks like this cropped up again with the upcoming 4.0 release. Even though I'm running 3.6 on my ubuntu 16.04.03 server with the 3.6 signing keys already downloaded, I started getting his same error. After deleting and reimporting the 3.6 keys as suggested in this thread, I ended up going back to James' original installation instructions and re-downloaded the key from there here It turns out that command actually downloads the 4.0 signing key, which resolved my problem:
| |||||||||||||||||||||||||||||
| Comment by Zakhar Kleyman [ 24/Oct/17 ] | |||||||||||||||||||||||||||||
|
James, Upon further review, I found that the error that you originally got was related to our rc release process. The steps I provided you turned out to do nothing to fix this. What actually resolved the problem was the 3.6.0-rc1 release that we did earlier today because it re-signed the repo with 3.6 key again. Once we release 3.6 GA, it would use a separate repo (xenial/mongodb-org/3.6), similarly to 3.4, so it will not be affected by any other branches. (You'd need to update /etc/apt/sources.list.d/mongodb-org-3.6.list though). We'll also work on fixing the RC release process to prevent issues like this in the future. I appologize for the incovinience it caused. | |||||||||||||||||||||||||||||
| Comment by James Newton [ 24/Oct/17 ] | |||||||||||||||||||||||||||||
|
Hi Zakhar, Your steps do seem to solve the issue. I had gone ahead and installed Thanks for your help! James $ sudo apt-key list pub 4096R/C0B21F32 2012-05-11 pub 4096R/EFE21092 2012-05-11 pub 1024D/FBB75451 2004-12-30 pub 4096R/91FA4AD5 2016-12-14 [expires: 2018-12-14] $ sudo apt-key del 91FA4AD5 Hit:3 http://mirrors.melbourne.co.uk/ubuntu xenial-backports InRelease Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:5 https://deb.nodesource.com/node_4.x xenial InRelease Ign:6 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/testing On 24 October 2017 at 20:54, Zakhar Kleyman (JIRA) <jira@mongodb.org> wrote: | |||||||||||||||||||||||||||||
| Comment by Zakhar Kleyman [ 24/Oct/17 ] | |||||||||||||||||||||||||||||
|
Hello, James. The steps you're using seem to be correct. I did everything you did on a fresh ubuntu 16.04.3 vagrant box and it worked ok for me. Can you please run "sudo apt-key list" on the box you're trying to install mongodb-org on and share the output? If 91FA4AD5 is there, can you try to delete it with "sudo apt-key del 91FA4AD5" and then re-import with the command below?
It should do the same thing as "sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5" but it pulls the key from our servers instead of ubuntu. It's the same key though. Update: You might also need to run "sudo apt-get update" in between deleting the key with apt-key del and re-adding it. |