Bug 668528

Summary:	Console installation doesn't show the broker unless triggered by event
Product:	Red Hat Enterprise MRG	Reporter:	William Henry <whenry>
Component:	cumin	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Jan Sarenik <jsarenik>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	1.3	CC:	jsarenik, tmckay
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-11 15:29: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:
Embargoed:

Description William Henry 2011-01-10 18:08:27 UTC

Description of problem:

If you follow the installation guide for the console including making sure there is a broker registered in the configuration file  (cumin.conf) the broker remains absent from the Messaging tab. 

An event like qpid-stat triggers some sort of change event which allows cumin to see the broker on the console UI. 

BTW any change my require an update to the documentation. Perhaps not, but maybe.


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

1.3

How reproducible:

Steps to Reproduce:
Install MRG Messaging as per MRG Messaging Installation guide.
Install the MRG Console as per the MRG Management Console Installation Guide.
Start the broker 
Start the console
Log into the console and go to the Messaging tab. There is no broker.
Wait as long as you'd like. (I ran it for a weekend.)
Then run qpid-stat -c
Look at the console and see that the broker now shows up.


1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Trevor McKay 2011-01-10 19:47:40 UTC

Note, this seems to be caused by a null value in the _systemRef_id field of the broker record in the postgres database.  Starting up a console causes this value to be filled in.

Comment 2 William Henry 2011-01-10 23:16:36 UTC

Retested from scratch to make sure that no steps in install/config were missed. 

I'm still seeing the same problem.

Comment 3 Jan Sarenik 2011-01-11 09:39:29 UTC

Before 1.3 release, I was told the needed workaround will be mentioned
in release notes. It probably wasn't. See bug 634975.

Comment 4 William Henry 2011-01-11 15:29:07 UTC


*** This bug has been marked as a duplicate of bug 634975 ***