+++ This bug was initially created as a clone of Bug #1434923 +++ Description of problem: Glance should usee v2.3 and Cinder should use v3 as the default api version for OSP10. Tracker - https://bugzilla.redhat.com/show_bug.cgi?id=1426284 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I want to clarify that we're talking about the API used by the CLI (both the cinder and osc versions). The cinder v3 endpoint was added in OSP-10 (see bug #1351271), but I confirmed both CLIs still default to v2. BTW, osc client support for cinder v3 was just added in Pike. Rajini, please confirm it's just the CLI versions that need to be bumped to v3.
It seems upstream support for cinder v3 in python-openstackclient (osc) is only a stub, and content is just being added [1]. I think the best we can hope for in the short term is to get python-cinderclient bumped to v3. [1] https://review.openstack.org/#/c/421585/
1. We should also authenticate using identity server API V3 This requires the overcloudrc to be changed Since Block Storage API V2 is officially deprecated, we should to set OS_VOLUME_API_VERSION=3. Also set the OS_AUTH_URL to the keystone endpoint: export OS_AUTH_URL=http://controller:5000/v3 export OS_VOLUME_API_VERSION=3 2.If a user makes a request without specifying a version, they will get the DEFAULT_API_VERSION as defined in cinder/api/openstack/api_version_request.py. Althought I'm not sure if this needs to be updated 3. Cinder V3 endpoint should be created in keystone openstack endpoint show cinderv3
Patch has been merged upstream, will update the BZ status once it's include in a build.
Clearing needsinfo (info provided in comment #11).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462