cinder client should retry when connection refused
Bug #1347843 reported by
Simon
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-cinderclient |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Currently, cinder client chooses not to retry when a connection to cinder is refused:
https:/
There are many legitimate scenarios that retries should be attempted:
1) cinder service is being restarted;
2) cinder service is behind a load balancer which may be temporarily overwhelmed.
In any case, retry with a back-off timer when connection is refused doesn't seem to hurt.
Revision history for this message
| Simon (xchenum) wrote | #1 |
| Changed in cinder: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Ivan Kolodyazhny (e0ne) wrote | #2 |
| affects: | cinder → python-cinderclient |
| Changed in python-cinderclient: | |
| status: | Triaged → Fix Committed |
| Changed in python-cinderclient: | |
| milestone: | none → 1.3.1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
A quick patch:
https:/