ConsistencyGroupsClient does not set api_version

Bug #1705556 reported by Chuck Fouts
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Invalid
Undecided
Unassigned

Bug Description

The ConsistencyGroupsClient does not set the api_version used by the inherited RestClient. During a post the api_version defaults to "v1" which in turn results in a 404 response.

Captured pythonlogging:
~~~~~~~~~~~~~~~~~~~~~~~
    2017-07-20 08:48:36,978 21246 INFO [tempest.lib.common.rest_client] Request (ConsistencyGroupsV2Test:test_create_consistencygroup_from_consistencygroup): 404 POST http://192.168.10.14:8776/v1/34576e3c
    2017-07-20 08:48:36,978 21246 DEBUG [tempest.lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'X-Auth-Token': '<omitted>', 'Accept': 'application/json'}
            Body: {"consistencygroup": {"name": "tempest-CG-1309862388", "volume_types": "48cba926-2c8e-4076-bade-a28ea4ad970a"}}
        Response - Headers: {'content-location': 'http://192.168.10.14:8776/v1/34576e3cd82e436e8e11d9ff3a7417e0/consistencygroups', u'content-type': 'application/json', u'content-length': '112', u'date': 'Thu
            Body: {"message": "The resource could not be found.<br /><br />\n\n\n", "code": "404 Not Found", "title": "Not Found"}

Setting the api_version = 'v2' fixes this issue.

Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Looks like this was supposed to be opened against tempest.

Appears to be working right in current tempest, so closing this.

Changed in python-cinderclient:
status: New → Invalid
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.