If a request fails but the response contains a "Retry-After",
the cinder client should wait the amount of time and then retry.
Cinder client should report a warning to user and continue with
retry, so that user can cancel the operation if not interested
in retry. The value in "Retry-After" header will be in seconds
or GMT value, client should handle both the cases.
How many times client should retry will be controlled by user
through "--retries" argument to cinder api example,
$ cinder --retries 3 availability-zone-list
If request was not sucessful within the retries, client should
raise the exception.
Reviewed: https:/ /review. openstack. org/332848 /git.openstack. org/cgit/ openstack/ python- cinderclient/ commit/ ?id=f8eef18297e c2dba4abf45f8ca 57c40c2380cad9
Committed: https:/
Submitter: Jenkins
Branch: master
commit f8eef18297ec2db a4abf45f8ca57c4 0c2380cad9
Author: Yuriy Nesenenko <email address hidden>
Date: Wed Jun 22 17:36:49 2016 +0300
Cinder client should retry with Retry-After value
If a request fails but the response contains a "Retry-After",
the cinder client should wait the amount of time and then retry.
Cinder client should report a warning to user and continue with
retry, so that user can cancel the operation if not interested
in retry. The value in "Retry-After" header will be in seconds
or GMT value, client should handle both the cases.
How many times client should retry will be controlled by user zone-list
through "--retries" argument to cinder api example,
$ cinder --retries 3 availability-
If request was not sucessful within the retries, client should
raise the exception.
Change-Id: I99af957bfbbe3a 202b148dc2fcafd d20b5d7cda0
Partial-Bug: #1263069