Skip to content
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

Closed
pulpbot opened this issue Jan 4, 2022 · 3 comments · Fixed by #733
Closed
Labels
.bugfix CHANGES/<issue_number>.bugfix
Milestone

Comments

@pulpbot
Copy link
Member

pulpbot commented Jan 4, 2022

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."

@pulpbot pulpbot added this to the Wishlist milestone Jan 4, 2022
@pulpbot
Copy link
Member Author

pulpbot commented Jan 4, 2022

From: @quba42 (quba42)
Date: 2021-04-27T15:30:57Z


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.

@stale
Copy link

stale bot commented May 25, 2022

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!

@stale stale bot added the stale label May 25, 2022
@quba42 quba42 added .bugfix CHANGES/<issue_number>.bugfix and removed Migrated from Redmine stale labels Aug 16, 2022
@quba42
Copy link
Collaborator

quba42 commented Aug 16, 2022

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.

Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
@quba42 quba42 linked a pull request Mar 9, 2023 that will close this issue
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 9, 2023
Manisha15 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.bugfix CHANGES/<issue_number>.bugfix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants