Bug 870467 - spacecmd interactive mode exits if wrong argument is entered
Summary: spacecmd interactive mode exits if wrong argument is entered
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aron Parsons
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space19
TreeView+ depends on / blocked
 
Reported: 2012-10-26 14:53 UTC by David Juran
Modified: 2013-03-06 15:56 UTC (History)
3 users (show)

Fixed In Version: spacecmd-1.9.3-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-03 22:36:53 UTC
Embargoed:

Attachments (Terms of Use)

Description David Juran 2012-10-26 14:53:59 UTC 
Description of problem:
If you in spacecmd interactive mode type an invalid parameter, e.g. snippet_update -n foo, the interactvie mode exits

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


Steps to Reproduce:
1. spacecmd
2. snippet_update -n foo

  
Actual results:

interactive mode exits and you get thrown out into your shell.
Comment 1 Miroslav Suchý 2012-10-29 13:53:47 UTC 
Forwarding to upstream.
Comment 2 Michael Mráka 2012-10-31 11:02:52 UTC 
Reassigning to spacecmd maintainer.
Comment 3 Steven Hardy 2013-02-21 11:49:18 UTC 
Reassigning to Aron Parsons, spacecmd maintainer
Comment 4 Aron Parsons 2013-03-03 22:36:53 UTC 
commit aa6d1c678db182185d0b7e0bd789719cd371eb79

This fixes the same issue throughout the whole application.  We needed to subclass OptionParser to change the error behavior.
Comment 5 Jan Pazdziora 2013-03-04 08:09:12 UTC 
Aron, we prefer to set the state to MODIFIED when changes were done for the bugzilla, fill the Fixed In Version (I did that now) and leave it for the release nanny to close the bugzilla when the new Spacewalk release is released.
Note You need to log in before you can comment on or make changes to this bug.