keystone user <username> gives misleading output
Bug #1100117 reported by
James Troup
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-keystoneclient |
Fix Released
|
Undecided
|
Unassigned | ||
| python-keystoneclient (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
This is python-
| root@gidim:~# keystone user-delete james
| No handlers could be found for logger "keystoneclient
| Could not find user: james (HTTP 404)
| root@gidim:~#
But it's not looking for a user; it's looking for a user ID:
| root@gidim:~# keystone help user-delete
| usage: keystone user-delete <user-id>
|
| Delete user
|
| Positional arguments:
| <user-id> User ID to delete
| root@gidim:~#
It'd be nice if it said 'Could not find user ID:' instead.
| Changed in python-keystoneclient (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
Revision history for this message
| Christophe Sauthier (christophe.sauthier) wrote | #1 |
| Changed in python-keystoneclient: | |
| status: | New → Fix Released |
| Changed in python-keystoneclient (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
The command actually produce a new output:
<user> Name or ID of user to delete
And you can provide both Name or ID.
So closing the bug.