Bug 782816

Summary:	warning messages of wallaby shell
Product:	Red Hat Enterprise MRG	Reporter:	Martin Kudlej <mkudlej>
Component:	wallaby	Assignee:	Will Benton <willb>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	low	Docs Contact:
Priority:	high
Version:	Development	CC:	esammons, ltoscano, ltrilety, matt, willb
Target Milestone:	2.3
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	wallaby-0.12.5-2	Doc Type:	Bug Fix
Doc Text:	Previous versions of the wallaby shell may have displayed a spurious warning message if no authentication mechanism was explicitly specified. Current versions will only display a warning if the explicitly-specified mechanism is invalid.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-06 18:40:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Kudlej 2012-01-18 15:36:50 UTC

Description of problem:

$ wallaby -M CRAM-MD5 -U guest -P guest list-groups
warning:  rejecting bogus WALLABY_BROKER_MECHANISM of ''
warning:  valid mechanisms include ANONYMOUS, CRAM-MD5, DIGEST-MD5, GSSAPI, OTP, PLAIN
Console Connection Established...
the default group +++DEFAULT
the skeleton group +++SKEL

$ cat  /etc/sysconfig/wallaby-agent 
...
export WALLABY_BROKER_MECHANISM=CRAM-MD5
...

I think first warning is not valid because authentication mechanism is defined in wallaby configuration and also as parameter of command.

I think there should be second warning only if user uses mechanism which is not supported by installed broker(it sends list of valid authentication mechanisms).


Version-Release number of selected component (if applicable):
ruby-wallaby-0.12.5-1
wallaby-0.12.5-1
python-wallabyclient-4.1.2-1
condor-wallaby-tools-4.1.2-1
condor-wallaby-base-db-1.19-1
condor-wallaby-client-4.1.2-1


How reproducible:
100%

Steps to Reproduce:
1. install broker, wallaby
2. install and configure auth. mechanism in broker/sasl/wallaby
3. run any command of wallaby shell

Comment 1 Will Benton 2012-01-18 18:36:27 UTC

This is fixed upstream; sorry to have missed it.

Comment 3 Will Benton 2012-03-20 14:18:41 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:
Previous versions of the wallaby shell may have displayed a spurious warning message if no authentication mechanism was explicitly specified.  Current versions will only display a warning if the explicitly-specified mechanism is invalid.

Comment 6 Lubos Trilety 2012-11-16 16:25:55 UTC

Successfully reproduce on:
ruby-wallaby-0.12.5-1
wallaby-0.12.5-1
wallaby-utils-0.12.5-1

# wallaby -M CRAM-MD5 -U cumin -P cumin list-groups
warning:  rejecting bogus WALLABY_BROKER_MECHANISM of ''
warning:  valid mechanisms include ANONYMOUS, CRAM-MD5, DIGEST-MD5, GSSAPI, OTP, PLAIN
Console Connection Established...
the default group +++DEFAULT
the skeleton group +++SKEL

Comment 7 Lubos Trilety 2012-11-16 16:31:43 UTC

Tested with:
wallaby-0.16.1-2
wallaby-utils-0.16.1-2
ruby-wallaby-0.16.1-2

Tested on:
RHEL6 i386,x86_64
RHEL5 i386,x86_64

No warning printed

# wallaby -M CRAM-MD5 -U cumin -P cumin list-groups
Console Connection Established...
the default group +++DEFAULT
the skeleton group +++SKEL

>>> verified

Comment 9 errata-xmlrpc 2013-03-06 18:40:58 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0564.html