Bug 1032103 - man packstack is missing options
Summary: man packstack is missing options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 4.0
Assignee: Ivan Chavero
QA Contact: Nir Magnezi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-19 14:48 UTC by Mohammed Arafa
Modified: 2013-12-20 00:37 UTC (History)
6 users (show)

Fixed In Version: openstack-packstack-2013.2.1-0.19.dev935.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-20 00:37:26 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 58715 0 None None None Never
OpenStack gerrit 58833 0 None None None Never
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description Mohammed Arafa 2013-11-19 14:48:13 UTC 
Description of problem:
i ran man packstack and compared it to the output of packstack --gen-answer-file=GEN_ANSWER_FILE

the answer file has more options that the man page. in my view the man page should be deprecated with a message that say "for options available to packstack run "packstack --gen-answer-file=GEN_ANSWER_FILE"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Ivan Chavero 2013-11-27 18:10:43 UTC 
Fixed some typos
Comment 3 Alvaro Lopez Ortega 2013-12-02 17:04:00 UTC 
Ivan, aside of the typos, the missing parameters are still missing.
Comment 4 Alvaro Lopez Ortega 2013-12-04 13:27:29 UTC 
Both 58715 and 58833 have been merged
Comment 8 errata-xmlrpc 2013-12-20 00:37:26 UTC 
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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html
Note You need to log in before you can comment on or make changes to this bug.