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
GPG error: following signatures were invalid: EXPKEYSIG 84ACD5B2D02945ED home:scylladb OBS Project <home:scylladb@build.opensuse.org> #5174
Comments
More serious issue touched in manual testing: Prepare:
Failed to
|
The key might be expired, please check and fix it. |
The issue should be fixed now. @amoskong, can you please retest? |
The problem still exists.
|
@amoskong which keyserver are you using to import the keys from? I now updated pgp.mit.edu, so it should work if you import from there. |
No, I see the problem. The key was extended but it was not propagated to the Release.key file. I now triggered a rebuild of scylla-gdb, when it completes it should propagate the key. |
I used
|
I updated keyserver.ubuntu.com now. |
@amoskong the debian 9 repo is refreshed now. |
Debian 8 as well. |
It works now, I saw the updated key.
|
I found the expired key is BTW, the It's better to set same expired data for all sign keys, then it's easy to maintain. |
@amoskong @avikivity |
How about this one?
|
+1 same issue here with this key provided in documentation 17723034C56D4B19 |
Hi @mehrdadpfg what's the error you touched? |
this was resolved and fixed - if there is still an issue please create a new issue with specific scylla version information and procedure |
Installation details
Scylla version (or git commit hash): latest 2.3, using private repo of 2.3
Cluster size:
OS (RHEL/CentOS/Ubuntu/AWS AMI):
Description:
Failed to install scylla 2.3 by private repo for auth issue, but it doesn't work from Oct 10, 2019.
ERROR:
Full logs:
Result
@roydahan
The text was updated successfully, but these errors were encountered: