Story #8873
closedpulp 3 stops when encounters 403 error
0%
Description
pulp 2, when encounters 403 errors it just moves on whereas pulp 3 stops and doesn't continue.
Files
Related issues
Updated by dkliban@redhat.com almost 3 years ago
- Tracker changed from Issue to Story
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
We should consider adding options for what errors are acceptable. I am converting this to a Story since this would be a new feature.
Updated by jsherril@redhat.com almost 3 years ago
- Tags Katello added
Katello is interested in this feature, but at a 'normal' priority
Updated by ipanova@redhat.com almost 3 years ago
- Is duplicate of Story #8881: As a user, Pulp will retry downloads by default 3 times and I can configure this value on my Remote added
Updated by ipanova@redhat.com almost 3 years ago
- Status changed from NEW to CLOSED - DUPLICATE
Updated by ipanova@redhat.com almost 3 years ago
- Is duplicate of deleted (Story #8881: As a user, Pulp will retry downloads by default 3 times and I can configure this value on my Remote)
Updated by ipanova@redhat.com almost 3 years ago
- Status changed from CLOSED - DUPLICATE to NEW
Updated by dalley almost 3 years ago
@mwaqas@bloombergindustry.com are there particular repositories where you frequently encounter this issue?
Updated by dalley almost 3 years ago
- Related to Issue #8787: "UnboundLocalError: local variable 'result' referenced before assignment" on attempt to sync some repos added
Updated by mwaqas@bloombergindustry.com almost 3 years ago
@mwaqas@bloombergindustry.com are there particular repositories where you frequently encounter this issue?
you can refer to ticket my colleague opened https://pulp.plan.io/issues/8875
Thanks!
Updated by dalley almost 3 years ago
So this ties into the retry discussion slightly. If one RPM fails to download (for any reason, be it 403, or repeated server errors, etc.) what should we do? Should the sync fail or should we fall back to making that one content unit "on_demand" and hope that the issue later resolves itself, or the RPM is never downloaded?
I think yes.
Updated by dalley almost 3 years ago
- Status changed from NEW to POST
- Assignee set to dalley
Updated by pulpbot almost 3 years ago
Updated by dalley almost 3 years ago
- Status changed from POST to CLOSED - DUPLICATE
- Assignee deleted (
dalley)
Closing in favor of https://pulp.plan.io/issues/5286 which has more detail and discussion
Updated by dalley almost 3 years ago
- Is duplicate of Story #5286: As a user, a Remote should provide an option that allows download errors, e.g. 404 errors to still allow creation of a RepositoryVersion added