Mismatched keystone api version produces cryptic 'Error: Openstack'

[Andrew Bogott]

The 'openstack' cli tool defaults to keystone version 2.0. When pointed to a v3 endpoint, it fails like this:

$ openstack service list
ERROR: openstack

This can easily be resolved by setting OS_IDENTITY_API_VERSION=3 -- that's not obvious from the error message, though, and isn't even obvious from log- and code-diving.

I propose that we actually detect the api version mismatch and error out with a helpful message.

[Lin Hua Cheng (lin-hua-cheng)]

Keystone is not responsible for the OSC command.

Tagging OSC, I agree the error message can be further improved

[Ruchi Parmar (ruchiparmar143)]

I am new to the community. Can you please guide me in solving the issue?

[Steve Martinelli (stevemar)]

Automatically unassigning due to inactivity.

[Steve Martinelli (stevemar)]

This is mostly fixed with our transition to keystoneauth:

stevemar@ubuntu:/opt/stack/keystone$ openstack user list
Could not determine a suitable URL for the plugin
stevemar@ubuntu:/opt/stack/keystone$ export OS_AUTH_URL='http://172.16.240.199:5000/v3'
stevemar@ubuntu:/opt/stack/keystone$ export OS_IDENTITY_API_VERSION='2.0'
stevemar@ubuntu:/opt/stack/keystone$ openstack user list
Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-77424210-16af-43a4-a560-6e3e42f1112d)
stevemar@ubuntu:/opt/stack/keystone$ export OS_USER_DOMAIN_NAME="Default"
stevemar@ubuntu:/opt/stack/keystone$ export OS_PROJECT_DOMAIN_NAME="Default"
stevemar@ubuntu:/opt/stack/keystone$ openstack user list
Ignoring domain related configs project_domain_name because identity API version is 2.0
Ignoring domain related configs user_domain_name because identity API version is 2.0
Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-e5be6625-7342-4a90-95f7-f9987f4a0e0b