Red Hat Bugzilla – Bug 904351
Provide keystone man page for the command line interface.
Last modified: 2016-04-26 15:03:11 EDT
The docs are currently in:
However there is no man subdir, which where the man pages are for eg. Keystone:
Started an upstream review on the master branch.
Work continues upstream to auto-generate man page from command line help (help2rst script), included here for the product is raw help2man generated manpage.
- there is no man page in python-keystoneclient-0.2.0-1.el6ost
- man page is present in python-keystoneclient-0.2.0-4.el6ost
Man pages corresponds with keystone help.
Except that description of 'discover' action is not complete.
Probably related to bug 888572.
------ snippet of `man keystone`
Update user’s name, email, and enabled status
Discover Keystone servers and show authentication protocols and
Grants a new role to a new user on a new tenant, after creating each.
------ snippet of `keystone help`
user-update Update user's name, email, and enabled status
discover Discover Keystone servers, supported API versions and
bootstrap Grants a new role to a new user on a new tenant, after
I see a keystone man page:
[root@localhost ~]# rpm -ql python-keystoneclient | grep man
[root@localhost ~]# man keystone | head -1
KEYSTONE(1) User Commands KEYSTONE(1)
Created attachment 753954 [details]
Screwed text in keystone manpage
The text in current manpage in python-keystoneclient-0.2.3-1.el6ost is really screwed up.
Lot of action/description pairs and whole lines are merged together to one big block of text. See the screenshot.
I replaced the broken help2man generated man page with a hand crafted one that is likely to be merged into upstream soon:
Broken content in man pages has been fixed according to gerrit.
I'd like to correct myself: The content has been sucessfully fixed in package python-keystoneclient-0.2.3-2.el6ost (as same as it is on gerrit #20976)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.