syncing deb repo with invalid/incorrect gpg key produces "No valid Release file found" error
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."
- Sprint/Milestone set to Wishlist
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.
Please register to edit this issue