python-cinderclient always requires latest microversion
Bug #1813967 reported by
Mathieu Gagné
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-cinderclient |
Fix Released
|
Undecided
|
Sean McGinnis | ||
Bug Description
Since this change [1], the cinder client will always use the latest microversion. This means if a Cinder server doesn't have the latest microversion as defined by the client, all calls will fail with an error similar to this one:
ERROR: Version 3.52 is not supported by the API. Minimum is 3.0 and maximum is 3.43. (HTTP 406)
Reverting the change made it possible to use the cinder client against a Cinder server which isn't the latest.
Forcing OS_VOLUME_
| Changed in cinder: | |
| assignee: | nobody → Sean McGinnis (sean-mcginnis) |
| importance: | Undecided → Medium |
Revision history for this message
| Eric Harney (eharney) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/python-cinderclient 4.2.0 | #2 |
| Changed in cinder: | |
| status: | New → Fix Released |
| Changed in cinder: | |
| status: | Fix Released → New |
| Changed in python-cinderclient: | |
| status: | New → Fix Released |
| assignee: | nobody → Sean McGinnis (sean-mcginnis) |
| no longer affects: | cinder |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/python-cinderclient 4.3.0 | #3 |
To post a comment you must log in.
https:/