Bug 782816 – warning messages of wallaby shell

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 782816 - warning messages of wallaby shell

Summary:	warning messages of wallaby shell

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	wallaby (Show other bugs)
Sub Component:
Version:	Development
Hardware:	Unspecified Unspecified

Priority	high Severity low
Target Milestone:	2.3
Target Release:	---
Assigned To:	Will Benton
QA Contact:	Lubos Trilety
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-01-18 10:36 EST by Martin Kudlej
Modified:	2013-03-06 13:40 EST (History)
CC List:	5 users (show)

See Also:
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 13:40:58 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0564	normal	SHIPPED_LIVE	Low: Red Hat Enterprise MRG Grid 2.3 security update	2013-03-06 18:37:09 EST

Groups: None (edit)

Description Martin Kudlej 2012-01-18 10:36:50 EST

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 13:36:27 EST

This is fixed upstream; sorry to have missed it.

Comment 3 Will Benton 2012-03-20 10:18:41 EDT

    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 11:25:55 EST

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 11:31:43 EST

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 13:40:58 EST

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

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