Actions
Issue #8511
closedsyncing deb repo with invalid/incorrect gpg key produces "No valid Release file found" error
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:
Description
Ticket moved to GitHub: "pulp/pulp_deb/399":https://github.com/pulp/pulp_deb/issues/399
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."
Updated by quba42 over 3 years ago
- 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.
Updated by pulpbot almost 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions