cinderclient retry in case of "retry-after" response recieved in response header
Registered by
Sheel Rana
cinder client retry in case "retry-after" response received in response header.
One bug is already open for this. But as this is not a bug rather required feature, raising blue print for same.
(Moved bug to wishlist)
I will add some more details about fix approach in a while.
JFR, https:/
Blueprint information
- Status:
- Not started
- Approver:
- Sean McGinnis
- Priority:
- Undefined
- Drafter:
- Sheel Rana
- Direction:
- Approved
- Assignee:
- Sheel Rana
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Bug #1263069: python bindings do not provide retry on rate limiting errors | Fix Released |
Sprints
Whiteboard
(?)