Story #8873
closed
pulp 3 stops when encounters 403 error
Status:
CLOSED - DUPLICATE
Description
pulp 2, when encounters 403 errors it just moves on whereas pulp 3 stops and doesn't continue.
Files
- 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.
Katello is interested in this feature, but at a 'normal' priority
- 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
- Status changed from NEW to CLOSED - DUPLICATE
- 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)
- Status changed from CLOSED - DUPLICATE to NEW
@mwaqas@bloombergindustry.com are there particular repositories where you frequently encounter this issue?
- Related to Issue #8787: "UnboundLocalError: local variable 'result' referenced before assignment" on attempt to sync some repos added
@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!
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.
- Status changed from NEW to POST
- Assignee set to dalley
- Status changed from POST to CLOSED - DUPLICATE
- Assignee deleted (
dalley)
- 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
Also available in: Atom
PDF
.
