-
-
Notifications
You must be signed in to change notification settings - Fork 28
manage gpg key with apt::keyring #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
bb1d5fc to
3ce9cb4
Compare
smortex
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, added another reviewer as I do not use these modules and might miss something.
|
any news? |
|
Hi @techsk8 As far as I know the code already create the keyring file in /etc/apt/keyrings/elastic-keyring.asc. I'm afraid managing apt::keyring in this module won't solve your issue .. Are you having this issue on a fresh/new server or are you upgrading a server that already has the old gpg key installed? |
|
could you please share the content of /etc/apt/sources.list.d/elastic.list and the output of |
|
I suspect your issue is related to module upgrade 9.x -> 10.0.0 If I'm right `sudo apt-key del 46095ACC8548582C1A2699A9D27D666CD88E42B4' should solve this. |
3ce9cb4 to
6a6ba74
Compare
6a6ba74 to
d3b5adb
Compare
Nope, I don't see v 10.0.0 using |
Fixes