Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 915774

Summary:	qpid-tool to have -b option as other qpid tools
Product:	Red Hat Enterprise MRG	Reporter:	Pavel Moravec <pmoravec>
Component:	qpid-tools	Assignee:	Ernie <eallen>
Status:	CLOSED ERRATA	QA Contact:	Irina Boverman <iboverma>
Severity:	low	Docs Contact:
Priority:	medium
Version:	2.3	CC:	iboverma, jross, lzhaldyb
Target Milestone:	3.0	Keywords:	Improvement
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	qpid-tools-0.22-3.el6, qpid-tools-0.22-3.el5	Doc Type:	Enhancement
Doc Text:	To align qpid-tool with functionality provided by other qpid tools, a "-b" command line option is now available to specify a broker address. The parameter takes the same form as the other qpid tools.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-24 15:06:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Moravec 2013-02-26 13:38:53 UTC

Description of problem:
Since qpid 0.18, almost all qpid tools like qpid-stat, qpid-config or so have -b option to specify broker URL. qpid-tool does not, specifying the URL without an option.

Since qpid-tool will have several other options (https://bugzilla.redhat.com/show_bug.cgi?id=710429, https://bugzilla.redhat.com/show_bug.cgi?id=895515 and https://bugzilla.redhat.com/show_bug.cgi?id=710429#c4), it makes sense to add -b to align it to other tools


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


How reproducible:
100%


Steps to Reproduce:
qpid-tool -b localhost:5001


Actual results:
Don't work


Expected results:
It works.


Additional info:

Comment 1 Ernie 2013-04-29 20:17:20 UTC

This was added with the patch for bug 710429. 
http://svn.apache.org/viewvc?view=revision&revision=1471120

Comment 4 errata-xmlrpc 2014-09-24 15:06:33 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/RHEA-2014-1296.html