Bug 619844

Summary: Wallaby utils should fail with a descriptive message when they can't connect to the store
Product: Red Hat Enterprise MRG Reporter: Will Benton <willb>
Component: wallaby-utilsAssignee: Will Benton <willb>
Status: CLOSED ERRATA QA Contact: Lubos Trilety <ltrilety>
Severity: medium Docs Contact:
Priority: low    
Version: DevelopmentCC: ltrilety, matt
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Will Benton 2010-07-30 17:05:32 UTC 
Description of problem:

The error message that the wallaby utilities display when they fail to connect to the wallaby agent is generally unhelpful.

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

0.6.3-1

Actual results:

QMF method calls will fail because the variable that should have a store object is nil, giving an "undefined method for nil:NilClass" error.

Expected results:

It would be more helpful for the tools to fail with a meaningful error message in this case.
Comment 1 Will Benton 2010-08-03 06:59:33 UTC 
This is fixed in 0.9.0.
Comment 2 Lubos Trilety 2010-10-15 12:35:18 UTC 
# service wallaby stop
# wallaby inventory
Console Connection Established...
fatal:  cannot find a wallaby agent on the specified broker (localhost:5672); is one running?
use -h for help

Tested with (version):
condor-wallaby-client-3.6-6.el5
wallaby-utils-0.9.18-2.el5
ruby-wallaby-0.9.18-2.el5
condor-wallaby-base-db-1.4-5.el5
python-wallabyclient-3.6-6.el5
condor-wallaby-tools-3.6-6.el5
wallaby-0.9.18-2.el5

Tested on:
RHEL5 i386,x86_64  - passed

>>> VERIFIED