Bug 612425 - [RFE] indefinite attempts to use bad credentials
[RFE] indefinite attempts to use bad credentials
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby-utils (Show other bugs)
Development
All Linux
low Severity low
: 1.3
: ---
Assigned To: Will Benton
Lubos Trilety
: FutureFeature
Depends On: 620912
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-08 03:48 EDT by Lubos Trilety
Modified: 2010-10-20 07:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 620912 (view as bug list)
Environment:
Last Closed:
Type: ---
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 Lubos Trilety 2010-07-08 03:48:05 EDT
Description of problem:
Any of wallaby tools from package 'wallaby-utils' needs correct user login and password. Problem is when the bad credentials are used. The tool tries to use them indefinitely.

Version-Release number of selected component (if applicable):
wallaby-utils-0.6.1-2

How reproducible:
100%

Steps to Reproduce:
1. run wallaby-inventory with bad credentials
  
Actual results:
The tool attempts to use the bad credentials indefinitely
The tool repeat the same message over and over again
'warning Broker closed connection: 320, connection-forced: Authentication failed'

Expected results:
After three or defined number of attempts the tool stops running
Comment 1 Will Benton 2010-08-25 19:03:48 EDT
There is a workaround for this issue in 0.9.6; the tools will time out after 15 seconds if they cannot connect to a broker.
Comment 2 Lubos Trilety 2010-10-15 08:38:57 EDT
Tested with (version):
wallaby-utils-0.9.18-2.el5
ruby-wallaby-0.9.18-2.el5
condor-wallaby-base-db-1.4-5.el5
wallaby-0.9.18-2.el5

Tested on:
RHEL5 i386,x86_64  - passed

>>> VERIFIED

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