-
Notifications
You must be signed in to change notification settings - Fork 78
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
syncing deb repo with invalid/incorrect gpg key produces "No valid Release file found" error #399
Comments
From: @quba42 (quba42) I believe this is so by design: Pulp deb simply discards any release files that fail to validate, if none are left, we get the error. I will take this ticket as a feature request for a clearer error message, which strikes me as valid enough. |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! |
This has once again led to user confusion: https://community.theforeman.org/t/ubuntu-repo-sync-not-working/29950 We should work on this issue. |
Author: @jlsherrill (jsherril@redhat.com)
Redmine Issue: 8511, https://pulp.plan.io/issues/8511
A katello user reported this: https://projects.theforeman.org/issues/32145
which seemed like a purely pulp issue.
"Error doesn't make it clear that the issue with Release integrity check failing, or that key is invalid.
There is nothing in the dynflow console either."
The text was updated successfully, but these errors were encountered: