When disabling or enabling a user, the client assumes "default" domain
Bug #1658147 reported by
Anne Gentle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
High
|
Samuel Pilla |
Bug Description
I'm using a private cloud as an admin that has no domain named "default."
But when issuing this command, I see that the project_domain_id passed in is default, and I don't see any way to tell the client which domain context I'm in.
$ openstack --debug user set interop --disable
Here's the relevant debug info that makes me think this is the case:
Using parameters {'username': 'agentle', 'password': '***', 'project_name': 'STAGE1-TW', 'user_domain_id': '3efc7152f9c245
Changed in python-openstackclient: | |
assignee: | nobody → Samuel Pilla (samuel.pilla) |
To post a comment you must log in.
To specify the domain context you are in, you can set it with an env. var or as a flag. Here are some examples:
if you're using a domain named 'default'
$ env | grep OS DOMAIN_ ID=default NAME=RegionOne DOMAIN_ ID=default NAME=admin API_VERSION= 3 openstack 172.16. 240.205: 5000/v3
OS_PROJECT_
OS_REGION_
OS_USER_
OS_PROJECT_
OS_IDENTITY_
OS_PASSWORD=
OS_AUTH_URL=http://
OS_USERNAME=admin
or if you're using a non-default domain
$ env | grep OS DOMAIN_ NAME=ibm NAME=RegionOne DOMAIN_ NAME=ibm NAME=my_ project API_VERSION= 3 humptydumpty 172.16. 240.205: 5000/v3 stevemar
OS_PROJECT_
OS_REGION_
OS_USER_
OS_PROJECT_
OS_IDENTITY_
OS_PASSWORD=
OS_AUTH_URL=http://
OS_USERNAME=
Not that you specify either OS_USER_DOMAIN_NAME or OS_USER_DOMAIN_ID, never both. Same goes for OS_PROJECT_ DOMAIN_ NAME and OS_PROJECT_ DOMAIN_ ID.