keystone-manage returns unhelpful text when arguments are missing
Bug #884947 reported by
Daniel Ford
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
High
|
Dolph Mathews | ||
Bug Description
For example:
$keystone-manage
No obj type specified for first argument
$keystone-manage tenant
No command specified for second argument
It would be nice if the list of acceptable values for these arguments was printed out.
| Changed in keystone: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in keystone: | |
| assignee: | nobody → Dolph Mathews (dolph) |
| milestone: | none → essex-3 |
| tags: | added: keystone-manage |
| Changed in keystone: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
This is fixed along with the rewrite of keystone-manage (bp keystone-manage2).
Commands now provide fairly verbose usage.
$ ./bin/keystone-
usage: create_tenant [-h] [--disabled] --name NAME [--id ID]
create_tenant: error: argument --name is required
$ ./bin/keystone-
usage: create_tenant [-h] [--disabled] --name NAME [--id ID]
Creates a new tenant, enabled by default. The tenant is enabled by default,
but can optionally be disabled upon creation.
optional arguments:
-h, --help show this help message and exit
--disabled create the tenant in a disabled state (tenants are enabled by
--name NAME a unique name
--id ID a unique identifier used in URLs