When resolving the user positional argument to the "user-get" command, keystoneclient uses the following logic:
# first try to get entity as integer id
try:
if isinstance(name_or_id, int) or name_or_id.isdigit():
return manager.get(int(name_or_id))
except exceptions.NotFound:
pass
# now try to get entity as uuid
try:
uuid.UUID(str(name_or_id))
return manager.get(name_or_id)
except (ValueError, exceptions.NotFound):
pass
When using a readonly LDAP server as the identity store, userids are strings instead of integers or UUIDs. Thus user lookups fail with a exceptions.NotFound exception.
[root@virt-three keystone]# keystone user-list
+------------+--------------------+---------+---------------------------+
| id | name | enabled | email |
+------------+--------------------+---------+---------------------------+
| admin | Administrator | False | |
...
| rdo-admin | RDO Administrator | True | <email address hidden> |
+------------+--------------------+---------+---------------------------+
[root@virt-three keystone]# keystone user-get rdo-admin
No user with a name or ID of 'rdo-admin' exists.
The attached patch resolves this issue by adding a third search attempt with the userid cast as a string:
[root@virt-three keystone]# keystone user-get rdo-admin
+----------+---------------------------+
| Property | Value |
+----------+---------------------------+
| email | <email address hidden> |
| enabled | True |
| id | rdo-admin |
| name | RDO Administrator |
+----------+---------------------------+
Any chance you can put that patch up for review on gerrit?