Default install of latest python-openstackclient fails to recognize the OS_DOMAIN_NAME environment variable

[Timothy Symanczyk]

On a brand new machine, installed the latest version of python-openstackclient (2.0.0) via pip. Using an old known-working domain-scoped rc file, the token issue command would return :

openstack token issue
Missing parameter(s):
Set a scope, such as a project or domain, set a project scope with --os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name

pip list reveals that it chose to install os-client-config (1.14.0) as part of the above.

Uninstalling os-client-config version 1.14.0, and installing version 1.12.0 resolves the issue.

Edit :
export OS_AUTH_URL=[our_keystone_url]
export OS_IDENTITY_API_VERSION=3
export OS_USERNAME=timothy_symanczyk
export OS_PASSWORD=[my_password]
export OS_REGION_NAME=[our_region]
export OS_DOMAIN_NAME=Default

[Steve Martinelli (stevemar)]

since pulling in os-client-config we've since offloaded a lot of the logic for auth to that project.

this has caused OS_DOMAIN_NAME to exhibit funky behaviour.

can you test this out with OS_DOMAIN_NAME removed/unset and OS_USER_DOMAIN_NAME and OS_PROJECT_DOMAIN_NAME set instead?

[Jonathan Thorpe (jon-thorpe)]

I can confirm that with OS_DOMAIN_NAME unset and OS_USER_DOMAIN_NAME and OS_PROJECT_DOMAIN_NAME set with python-openstackclient 2.0.0 and os-client-config 1.14.0 I can successfully authenticate and perform commands against the domain.

[Jonathan Thorpe (jon-thorpe)]

I made a mistake in my previous comment. I meant to say when I am project scoped I can execute commands against the PROJECT, not the domain.

[Timothy Symanczyk (timothy-symanczyk)]

Yes, Jonathan absolutely - the bug report is explicitly against being able to authenticate at the domain level. The client can still authenticate and operate at the project level as far as I've seen.

Steve was that your question? I wasn't sure if you had intended for me to set and test OS_PROJECT_NAME. Either way I tried what you had asked literally, and the error was the same (missing parameters). Which is what I would've expected, because to the best of my knowledge the python-openstackclient doesn't seems required a scoped token.

[Dean Troyer (dtroyer)]

Numerous changes have been made to os-client-config and OSC since the last comments here specifically around the domain/project handling during authentication. If this is still an issue, feel free to re-open it against the current releases of both projects.