[SERVER-31459] GPG Error - KEYEXPIRED 1507497109 Created: 09/Oct/17  Updated: 30/Oct/23  Resolved: 09/Oct/17

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

Type: Bug Priority: Major - P3
Reporter: Adithya Varma Bhupathiraju Assignee: Ernie Hershey
Resolution: Fixed Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Build Ready
Participants:
Case:

 Description   

I have followed the mongodb official doc to install mongodb 3.2 on Ubuntu 14.04.
But when I exec "apt-get update", it will raise an error:


W: GPG error: http://repo.mongodb.org trusty/mongodb-org/3.2 Release: The following signatures were invalid: KEYEXPIRED 1507497109



 Comments   
Comment by Ernie Hershey [ 18/Oct/17 ]

Hi pchand - I believe you can re-run the same command from the docs:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927

You will probably get better visibility on similar questions in the future by posting to the mongodb-user mailing list.

Comment by Pradeep Chand [ 18/Oct/17 ]

Hey,
Could i get some help to update the key, I don't know the command. I am using Ubuntu 16.04. Thanks in advance.

Comment by Omer van Kloeten [ 10/Oct/17 ]

I can verify this works. Thank you for the swift response!

Comment by Ernie Hershey [ 09/Oct/17 ]

We've published a renewed public key in the following locations. Please comment on this ticket if you see any further related errors.

https://www.mongodb.org/static/pgp/server-3.2.asc
https://www.mongodb.org/static/pgp/server-3.2.pub
http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xD68FA50FEA312927

Comment by Ernie Hershey [ 09/Oct/17 ]

Hi. We're working to renew our 3.2 release series public PGP key and expect to have an update later this week.

Comment by Omer van Kloeten [ 09/Oct/17 ]

+1 can verify this happens for us too. Should we use --force-yes? I won't until I hear back from the team that it's OK.

Also, I believe this issue should be classified as Critical, not Major.

Generated at Thu Feb 08 04:27:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.