Bug 833870 - wallaby cluster-sync-to-store with bad ricci password should return non-zero exit code and inform user about it
wallaby cluster-sync-to-store with bad ricci password should return non-zero ...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby-utils (Show other bugs)
2.2
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: grid-maint-list
MRG Quality Engineering
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-20 09:52 EDT by Tomas Rusnak
Modified: 2016-05-26 16:10 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-26 16:10:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Rusnak 2012-06-20 09:52:42 EDT
Description of problem:
When you enter bad password wallaby cluster-sync-to-store for ricci, the result code is 0.

I think, the better should be to return some error code. Also we can add some info message that password is wrong or so.

Version-Release number of selected component (if applicable):
python-wallabyclient-4.1.2-1.el6.noarch
condor-wallaby-client-4.1.2-1.el6.noarch
condor-wallaby-tools-4.1.2-1.el6.noarch
condor-wallaby-base-db-1.22-4.el6.noarch
ruby-wallaby-0.12.5-1.el6.noarch
wallaby-0.12.5-1.el6.noarch
wallaby-utils-0.12.5-1.el6.noarch


How reproducible:
100%

Steps to Reproduce: 
1. wallaby cluster-sync-to-store --riccipassword pokemon
Console Connection Established...
2. echo $?
0
3. check messages for error:
Jun 20 13:20:12 rhel-ha-1 saslauthd[1862]: do_auth         : auth failure: [user=ricci] [service=ricci] [realm=] [mech=pam] [reason=PAM auth error]

  
Actual results:
when bad password was entered result code is 0

Expected results:
result code should be non-zero and information message should be in place

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