Bug 746988

Summary:	When Cumin is connected to multiple brokers the 'Connections' tab does not filter connections by broker
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	cumin	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	eallen, jross, matt
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-26 19:37:07 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 Trevor McKay 2011-10-18 13:49:14 UTC

Description of problem:

Connected Cumin to 3 brokers.  Drilled into each broker, went to the Connections tab.  All of the connections for all 3 brokers are displayed under the Connections tab for each of the brokers.  The list should be filtered for the particular broker.

Discovered while investigating customer questions.

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

This code hasn't changed for quite a while, assuming 2.0 (or even 1.3) but I haven't tested that.

How reproducible:

100%

Steps to Reproduce:
1.  Specify multiple brokers in the cumin.conf file.
2.  Drill into each and look at the connections.  Connections can be differentiated by looking at the IP addresses involved, or by running different apps on different hosts (condor, qpid-tool, qpid-stat, etc)
  
Actual results:

All connections in the Cumin database are displayed.

Expected results:

Connections ought to be filtered by broker we've drilled into to get to the Connections tab.

Additional info:

It seems to me that Exchanges, Queues, etc are working correctly but we might want to check those too.

Comment 1 Anne-Louise Tangring 2016-05-26 19:37:07 UTC

MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.