python bindings do not provide retry on rate limiting errors
Bug #1263069 reported by
Andrea Frittoli
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance Client |
Confirmed
|
Wishlist
|
Unassigned | ||
python-cinderclient |
Fix Released
|
Wishlist
|
Yuriy Nesenenko | ||
python-heatclient |
Triaged
|
Medium
|
Unassigned | ||
python-keystoneclient |
Won't Fix
|
Wishlist
|
Unassigned | ||
python-neutronclient |
Confirmed
|
Wishlist
|
Unassigned | ||
python-novaclient |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
The openstack python bindings do not provide retries on rate limiting errors.
This is a missing feature rather than a bug.
It would be both useful for users as well as for tempest tests (see https:/
Changed in python-keystoneclient: | |
importance: | Undecided → Wishlist |
summary: |
- python bindings do not provide rerty on rate limiting errors + python bindings do not provide retry on rate limiting errors |
Changed in python-keystoneclient: | |
status: | New → Triaged |
Changed in python-novaclient: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in python-heatclient: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → v0.2.8 |
Changed in python-cinderclient: | |
assignee: | nobody → venkata anil (anil-venkata) |
Changed in python-cinderclient: | |
status: | New → In Progress |
Changed in python-cinderclient: | |
status: | In Progress → Fix Committed |
Changed in python-cinderclient: | |
status: | Fix Committed → In Progress |
Changed in python-heatclient: | |
milestone: | v0.2.8 → v0.2.9 |
Changed in python-heatclient: | |
assignee: | Chmouel Boudjnah (chmouel) → nobody |
Changed in python-heatclient: | |
milestone: | v0.2.9 → none |
importance: | High → Medium |
Changed in python-glanceclient: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in python-cinderclient: | |
assignee: | venkata anil (anil-venkata) → nobody |
Changed in python-cinderclient: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in python-cinderclient: | |
importance: | Undecided → Wishlist |
Changed in python-cinderclient: | |
status: | In Progress → Confirmed |
assignee: | nobody → Sheel Rana (ranasheel2000) |
Changed in python-cinderclient: | |
assignee: | Sheel Rana (ranasheel2000) → Yuriy Nesenenko (ynesenenko) |
Changed in python-neutronclient: | |
assignee: | nobody → lilintan (lilintan) |
Changed in python-novaclient: | |
assignee: | nobody → Spencer Yu (yushb) |
Changed in python-neutronclient: | |
assignee: | lilintan (lilintan) → nobody |
Changed in python-novaclient: | |
assignee: | Spencer Yu (yushb) → Jeremy Liu (liujiong) |
Changed in python-novaclient: | |
assignee: | Jeremy Liu (liujiong) → Spencer Yu (yushb) |
Changed in python-novaclient: | |
assignee: | Spencer Yu (yushb) → Jeremy Liu (liujiong) |
Changed in python-novaclient: | |
assignee: | Jeremy Liu (liujiong) → Spencer Yu (yushb) |
Changed in python-novaclient: | |
status: | In Progress → Confirmed |
assignee: | Spencer Yu (yushb) → nobody |
importance: | Medium → Wishlist |
To post a comment you must log in.
I'm personally not sure how useful would this be, it seems to go against the purpose of the limits. Yet if it gets implemented maybe the clients should honor the "Retry-After" passed by the server?