Cinder microversion 3.40 not matching 3.27, treated as 3.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cinderclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Using change in https:/
Using the above new Cinder v3.27 API change, nova (in nova.volume.
attachment_ref = cinderclient(
This is throwing an exception CinderAPIVersio
The problem is in python-
line 32: MAX_VERSION = "3.40"
I believe this is happening because the max version is getting interpreted as 3.4, not 3.40 (the end zero is getting dropped) and when that is compared to 3.27, the match is failing.
Some detail:
nova/volume/
(Pdb) url
u'http://
(Pdb) microversion
'3.27
max_api_version = cinder_
(Pdb) max_api_version
3.4
max_api_version = cinder_
(Pdb) max_api_version
<APIVersion: 3.4>
(Pdb) max_api_
4
Changed in python-cinderclient: | |
assignee: | Gorka Eguileor (gorka) → Steve Noyes (steve-noyes) |
assignee: | Steve Noyes (steve-noyes) → nobody |
it's definitely a cinder client issue. I changed MAX_VERSION to "3.4" (from "3.40") and cinder_ client. get_highest_ client_ server_ version( url) still returns a float 3.4.