discover_version ignores client max supported version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cinderclient |
Fix Released
|
Undecided
|
Brian Rosmaita |
Bug Description
Using a stable/rocky client in a master (Train) devstack:
Python 2.7.12 (default, Nov 12 2018, 14:36:49)
>>> # (skipping auth setup)
>>>
>>> from cinderclient import client
>>> cinder = client.Client('3', session=session)
>>>
>>> # get highest supported mv from client
>>> from cinderclient import api_versions as mv
>>> mv.MAX_VERSION
'3.52'
>>>
>>> # get highest supported mv from server
>>> highest_v = mv.get_
>>> highest_v
<APIVersion: 3.59>
>>>
>>> # discover the max supported version for this session
>>> mv.discover_
<APIVersion: 3.59>
Expected to discover that the max supported version is 3.52
The docstring for discover_version() says:
Checks ``requested_
On the plus side, discover_version() doesn't seem to be used anywhere in the code. But as a convenience method for developers, it would be nice for it to be accurate.
Changed in python-cinderclient: | |
status: | New → In Progress |
Assumning this is a defect, it is currently present in master cinderclient.