Issue #4434
Some ClientResponseError can't try additional Remotes
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Description
@gmbnomis pointed out with this comment that a ClientResponseError cannot continue to the next Remote in some cases.
We need to only try additional Remotes if the ClientResponseError is experienced before any data has been streamed to the client.
History
#1
Updated by CodeHeeler over 1 year ago
- Triaged changed from No to Yes
#2
Updated by bmbouter about 1 year ago
- Tags deleted (
Pulp 3)
Please register to edit this issue
.