[DOCS-13691] Provided signing key does not match Debian buster packages Created: 08/Jun/20 Updated: 30/Oct/23 Resolved: 09/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Johannes Wienke | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | debian, signing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 3 years, 35 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 09/Jun/20 ] | |
|
Thanks for your patience everyone. We appreciate the outreach. | |
| Comment by Johannes Wienke [ 09/Jun/20 ] | |
|
Yes, also works again on our side. | |
| Comment by Alon Reznik [ 09/Jun/20 ] | |
|
Hi Ravind. Seems to be fixed.
Thanks for all of the help
Alon | |
| Comment by Ravind Kumar (Inactive) [ 08/Jun/20 ] | |
|
Hey folks! Our engineers deployed changes to fix the affected repositories. Please let us know if there are continued issues for deployment. We're also exploring mitigations to prevent this issue from happening again. | |
| Comment by Ravind Kumar (Inactive) [ 08/Jun/20 ] | |
|
Hi alon@rivery.io, We have multiple engineers actively working on this issue. I've notified them of the deployment blocker as well. We appreciate your patience. As soon as our team knows of a fix, we will update this ticket. | |
| Comment by Alon Reznik [ 08/Jun/20 ] | |
|
Hi Guys. I think you already know that this blocking any deployments using Docker(s) that includes your package. If not - please prioritize this a critical due to it blocks our deployments for now. Thanks! | |
| Comment by Ravind Kumar (Inactive) [ 08/Jun/20 ] | |
|
Thanks for letting us know - our engineers are aware of the issue and are investigating. It looks like the release may have been signed with the MongoDB 4.4 key. You can install that key as a temporary work-around:
See Step 1 of our 4.4 Installation Instructions for more information. I understand this is inconvenient. Once the issue is resolved, you should no longer require the 4.4 public key for installing 4.2-series binaries. I can leave this ticket open and resolve once the issue has been addressed. |