Project

Profile

Help

Issue #4434

Some ClientResponseError can't try additional Remotes

Added by bmbouter about 2 years ago. Updated almost 2 years ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

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 about 2 years ago

  • Triaged changed from No to Yes

#2 Updated by bmbouter almost 2 years ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF