cinder list does weird things if pointed at a v1 endpoint with OS_VOLUME_API_VERSION=2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cinderclient |
Fix Released
|
Undecided
|
Anastasia Latynskaya |
Bug Description
ubuntu@devstack:~$ . ~/devstack/openrc
ubuntu@devstack:~$ cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 50b24c25-
| d8a9e6c5-
+------
ubuntu@devstack:~$ export OS_VOLUME_
ubuntu@devstack:~$ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 50b24c25-
| d8a9e6c5-
+------
Note that when using the v2 api, we use "Name" instead of "Display Name" but the field in the volumes table in the db is display_name so it needs to be translated during display.
Changed in cinder: | |
status: | New → Confirmed |
summary: |
- cinder list fails to display volume name if using v2 of api + cinder list does weird things if pointed at a v1 endpoint with + OS_VOLUME_API_VERSION=2 |
Changed in cinder: | |
status: | Invalid → New |
Changed in python-cinderclient: | |
status: | New → In Progress |
assignee: | nobody → Anastasia Latynskaya (alatynskaya) |
no longer affects: | cinder |
Changed in python-cinderclient: | |
milestone: | none → 1.3.1 |
status: | Fix Committed → Fix Released |
Not sure if this is by design or not, but changing the api version on the client side does not call the actual v2 api on the server side hence the issue you see here. Calls are made to v1 even if you set v2 in cinder client. (see endpoints)