qos commands not working in api version 2

Bug #1284321 reported by Kurt Martin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
High
Mike Perez

Bug Description

I have the OS_VOLUME_API_VERSION set to 2, some of the 'cinder qos-key ... set/unset' commands are not working, giving the following error:
ERROR: Volume API version is set to 2 but you are accessing a 1 endpoint. Change its value via either --os-volume-api-version or env[OS_VOLUME_API_VERSION]

What doesn't work with OS_VOLUME_API_VERSION=2,
cinder qos-key 563055a9-f17f-4553-8595-4a948b5bf010 set latency=1000
cinder qos-key 563055a9-f17f-4553-8595-4a948b5bf010 unset latency
but if I set --os-volume-api-version=1 the following commands work:
cinder --os-volume-api-version=1 qos-key 563055a9-f17f-4553-8595-4a948b5bf010 set latency=1000
cinder --os-volume-api-version=1 qos-key 563055a9-f17f-4553-8595-4a948b5bf010 unset latency

What works with OS_VOLUME_API_VERSION=2
cinder qos-create test priority=high maxIOPS=10000
cinder qos-delete 08ab1436-6e82-4075-924d-7a4ee2394f7f
cinder qos-list
cinder qos-show 563055a9-f17f-4553-8595-4a948b5bf010
cinder qos-associate 563055a9-f17f-4553-8595-4a948b5bf010 71ca8337-5cbf-43f5-b634-c0b35808d9c4
cinder qos-disassociate 563055a9-f17f-4553-8595-4a948b5bf010 71ca8337-5cbf-43f5-b634-c0b35808d9c4

[stack@kurt-devstack:~]↥ 1 $ cinder qos-key 563055a9-f17f-4553-8595-4a948b5bf010 set latency=1000
ERROR: Volume API version is set to 2 but you are accessing a 1 endpoint. Change its value via either --os-volume-api-version or env[OS_VOLUME_API_VERSION]
[stack@kurt-devstack:~]↥ 1 $ env | grep OS_VOLUME_API_VERSION
OS_VOLUME_API_VERSION=2

[stack@kurt-devstack:~]↥ $ keystone endpoint-list
+----------------------------------+-----------+-------------------------------------------+-------------------------------------------+-------------------------------------------+----------------------------------+
| id | region | publicurl | internalurl | adminurl | service_id |
+----------------------------------+-----------+-------------------------------------------+-------------------------------------------+-------------------------------------------+----------------------------------+
| 1026066f9eb0402182c20e42239322fb | RegionOne | http://10.10.22.144:8774/v2/$(tenant_id)s | http://10.10.22.144:8774/v2/$(tenant_id)s | http://10.10.22.144:8774/v2/$(tenant_id)s | 6e43a189913f4089a7307d67bd06090e |
| 5920e801dc5e49eb92d2d12ac3413ebd | RegionOne | http://10.10.22.144:8773/services/Cloud | http://10.10.22.144:8773/services/Cloud | http://10.10.22.144:8773/services/Admin | 4551834a369e47c1b327b20de5de5fa1 |
| 63a85e728aba454fa72024c149087a00 | RegionOne | http://10.10.22.144:8776/v1/$(tenant_id)s | http://10.10.22.144:8776/v1/$(tenant_id)s | http://10.10.22.144:8776/v1/$(tenant_id)s | d68d24286568468f8e6b4aa5b2d655de |
| 7c63d18a72444350b261935061729482 | RegionOne | http://10.10.22.144:8776/v2/$(tenant_id)s | http://10.10.22.144:8776/v2/$(tenant_id)s | http://10.10.22.144:8776/v2/$(tenant_id)s | 02ba251f0dbd4e499f3d469396fb65e4 |
| a826acb8d73342deb907960df90e32c2 | RegionOne | http://10.10.22.144:5000/v2.0 | http://10.10.22.144:5000/v2.0 | http://10.10.22.144:35357/v2.0 | 30ecc7d5247c41eebbd8bd033b4cbe85 |
| b5e0dac178ea4dba9792fdf1e7f981aa | RegionOne | http://10.10.22.144:9292 | http://10.10.22.144:9292 | http://10.10.22.144:9292 | a8a3d88e94ef4fc78ded5dbaf356bdca |
| e02332879287473481439fe23d161274 | RegionOne | http://10.10.22.144:8774/v3 | http://10.10.22.144:8774/v3 | http://10.10.22.144:8774/v3 | dab409a3c0a14b018bcbd9ecb23fc643 |
| ff0e2fa4effc458b92f37f63db107d63 | RegionOne | http://10.10.22.144:3333 | http://10.10.22.144:3333 | http://10.10.22.144:3333 | 8d45b5eaf43c4ba69d1a3be79faeeb9b |
+----------------------------------+-----------+-------------------------------------------+-------------------------------------------+-------------------------------------------+----------------------------------+

Tags: api
description: updated
summary: - qos commands not working is api version 2
+ qos commands not working in api version 2
tags: added: api
Revision history for this message
Kurt Martin (kurt-f-martin) wrote :

Basically qos-key is not working in version 2 of the api, all the other commands are working in version 2 of the api

[stack@kurt-devstack:/opt/stack/cinder]↥ qos+* ± cinder help | grep qos
    qos-associate Associate qos specs with specific volume type.
    qos-create Create a new qos specs.
    qos-delete Delete a specific qos specs.
    qos-disassociate Disassociate qos specs from specific volume type.
    qos-disassociate-all
                        Disassociate qos specs from all of its associations.
    qos-get-association
                        Get all associations of specific qos specs.
    qos-key Set or unset specifications for a qos spec.
    qos-list Get full list of qos specs.
    qos-show Get a specific qos specs.

Mike Perez (thingee)
Changed in cinder:
importance: Undecided → High
status: New → In Progress
assignee: nobody → Mike Perez (thingee)
Mike Perez (thingee)
Changed in cinder:
milestone: none → icehouse-3
Revision history for this message
John Griffith (john-griffith) wrote :

Looks like there are some other commands impacted by this as well. The list-extensions command is the most recent I've discovered.

Thierry Carrez (ttx)
Changed in cinder:
milestone: icehouse-3 → icehouse-rc1
Revision history for this message
Mike Perez (thingee) wrote :
Revision history for this message
John Griffith (john-griffith) wrote :

Both of the above referenced patches have landed, marking as complete.

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: icehouse-rc1 → 2014.1
Revision history for this message
Ryan McNair (rdmcnair) wrote :
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/python-cinderclient 1.5.0

This issue was fixed in openstack/python-cinderclient 1.5.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.