Comment 3 for bug 1454369

Hi Jay, novaclient calls directly to cinder instead of using the nova proxy. It already defaults to using the 'volume' service type and I think the problem you're hitting is because of how devstack sets up the service types. If you take a look at the output of 'keystone catalog' you can see what urls are mapped for 'volume' and 'volumev2'. I suspect what is happening is you disabled the v1 api but 'volume' in the service catalog is pointing at /v1. In a real deployment, I think an operator would set up the service in the catalog as /v2 and "volume" endpoint and then the same scenario you tried would work fine.