Bug 668799 - wallaby help $COMMAND and wallaby $COMMAND -h should exit successfully
Summary: wallaby help $COMMAND and wallaby $COMMAND -h should exit successfully
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby-utils
Version: 1.3
Hardware: All
OS: Linux
low
medium
Target Milestone: 1.3.2
: ---
Assignee: Will Benton
QA Contact: Lubos Trilety
URL:
Whiteboard:
: 635975 668434 (view as bug list)
Depends On: 635628
Blocks: 668432
TreeView+ depends on / blocked
 
Reported: 2011-01-11 16:46 UTC by Will Benton
Modified: 2011-02-15 12:17 UTC (History)
4 users (show)

Fixed In Version: wallaby-0.10.4-2
Doc Type: Bug Fix
Doc Text:
The wallaby command exited with a non-zero exit code, used to indicate failure, even when the "help" subcommand was invoked. With this update, the wallaby command exits with an exit code of 0 (zero) when help is requested, as expected.
Clone Of: 635628
Environment:
Last Closed: 2011-02-15 12:17:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0217 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging and Grid bug fix and enhancement update 2011-02-15 12:10:15 UTC

Comment 1 Will Benton 2011-01-11 16:52:11 UTC 
*** Bug 635975 has been marked as a duplicate of this bug. ***
Comment 2 Will Benton 2011-01-11 16:54:15 UTC 
*** Bug 668434 has been marked as a duplicate of this bug. ***
Comment 3 Will Benton 2011-01-14 18:53:05 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C:  Wallaby utility commands exited with a failure status after printing their help messages.
C:  This behavior may have been confusing for some users.
F:  Wallaby utility commands now exit with a zero (success) status when help is requested.
R:  Users should find that the exit-status behavior of wallaby utility commands is now more consistent with their expectations.
Comment 5 Lubos Trilety 2011-01-27 14:31:37 UTC 
# wallaby help load
Usage:  wallaby load [SNAPFILE]
Loads a wallaby snapshot from a file or from standard input.
    -h, --help                       displays this message
    -a, --activate                   attempt to activate config after loading
    -q, --quiet                      do not provide progress on load feedback
    -v, --verbose                    provide more progress on load feedback

# echo $?
1

# rpm -q wallaby
wallaby-0.10.4-1.el5
Comment 7 Lubos Trilety 2011-01-28 12:47:30 UTC 
Tested with (version):
wallaby-0.10.4-2

Tested on:
RHEL5 i386,x86_64  - passed

>>> VERIFIED
Comment 8 Douglas Silas 2011-02-09 17:51:22 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-C:  Wallaby utility commands exited with a failure status after printing their help messages.
+The wallaby command exited with a non-zero exit code, used to indicate failure, even when the "help" subcommand was invoked. With this update, the wallaby command exits with an exit code of 0 (zero) when help is requested, as expected.-C:  This behavior may have been confusing for some users.
-F:  Wallaby utility commands now exit with a zero (success) status when help is requested.
-R:  Users should find that the exit-status behavior of wallaby utility commands is now more consistent with their expectations.
Comment 9 errata-xmlrpc 2011-02-15 12:17:38 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

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