Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #4434

closed

Some ClientResponseError can't try additional Remotes

Added by bmbouter about 5 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
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

Ticket moved to GitHub: "pulp/pulpcore/1819":https://github.com/pulp/pulpcore/issues/1819

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.

Actions
Copy link
 #1

Updated by CodeHeeler about 5 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #2

Updated by bmbouter about 5 years ago

  • Tags deleted (Pulp 3)
Actions
Copy link
 #3

Updated by pulpbot over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF