Comment 6 for bug 1154809

This is an incompatiblilty between v2 and v3 service catalogs. This only happens with UUID tokens currently.

Nova gets the service catalog from auth_token middleware and then passes that to cinderclient. The problem breaks down as follows:

Using PKI:

novaclient still uses v2.0 so it gets a v2.0 pki token. The auth_token middleware simply extracts the catalog from the token and passes it along. The catalog is in v2.0 format

Using uuid:
novaclient uses v2.0 and gets a v2.0 uuid token. The auth_token middleware uses the most recent (v3.0) api to validate the token so it gives back a v3.0 catalog. This catalog is then passed in to cinderclient which blows up.

So clearly cinderclient need to support parsing the new catalog, but in the meantime we can get around this issue by forcing nova to use the v2.0 api Unfortunately if people start sending in v3 PKI tokens we will see a similar issue, so we really need either:

a) something that can translate v3-v2 catalogs in nova or b) an updated cinderclient that can understand v3 catalogs.