Bug 797051 - unexpected wordwrap found in new 'rhc app' command help page
Summary: unexpected wordwrap found in new 'rhc app' command help page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 1.x
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: John (J5) Palmieri
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 06:21 UTC by Meng Bo
Modified: 2013-03-13 04:52 UTC (History)
3 users (show)

Fixed In Version: rhc-0.89.11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:30:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Meng Bo 2012-02-24 06:21:56 UTC
Description of problem:
unexpected wordwrap occurs when execute 'rhc app' or 'rhc-app' with -h or --help for --enable-jenkins option

Version-Release number of selected component (if applicable):
rhc-0.87.3-1.el6_2.noarch

How reproducible:
always

Steps to Reproduce:
1.install rhc client
2.run command 'rhc app -h'
3.
  
Actual results:
<------>
  --enable-jenkins [name]    Indicates to create a Jenkins application (if not
already available)
                             and embed the Jenkins client into this
application.  The default 
                             name will be 'jenkins' if not specified. Note that
--no-dns is ignored
                             for the creation of the Jenkins application.

Expected results:
The description of --enable-jenkins option should stay in one line and wordwrap
automatically. 

Additional info:
Please refer to related bug 768809 for old cli

Comment 1 John (J5) Palmieri 2012-03-30 21:03:58 UTC
fixed b5e70840b60f610709c94d53e6f6411d2cfc7e2f

Comment 2 Xiaoli Tian 2012-03-31 05:36:28 UTC
The latest rhc client is still rhc-0.89.10, rhc-0.89.11 is not built, please help to check what's missed?

Comment 3 Meng Bo 2012-04-01 02:58:32 UTC
verified with rhc-0.89.11-1.el6_2.noarch,
issue has been fixed.


Note You need to log in before you can comment on or make changes to this bug.