Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: CFME isn't currently subscribed to the heat rabbit exchange in the Openstack cloud provider. https://github.com/ManageIQ/manageiq/blob/master/config/vmdb.tmpl.yml#L291 Version-Release number of selected component (if applicable): 5.4.2 How reproducible: 100% Expected results: CFME should show up Heat events in the Openstack cloud provider timelines.
https://github.com/ManageIQ/manageiq/pull/5423
ignore comment #2 fix is in https://github.com/ManageIQ/manageiq/pull/5425
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/cbecd203a18d397b17ed237e705edc99e5d85e9e commit cbecd203a18d397b17ed237e705edc99e5d85e9e Author: Ladislav Smola <lsmola> AuthorDate: Fri Nov 13 13:47:06 2015 +0100 Commit: Ladislav Smola <lsmola> CommitDate: Fri Nov 13 13:47:06 2015 +0100 OpenStack catch Heat events OpenStack catch Heat events Implements BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1266141 config/vmdb.tmpl.yml | 1 + 1 file changed, 1 insertion(+)
I created a VIP for the message queue and I successfully validated the connection from CFME to rabbit. Still, I don't see any heat events (I created and deleted a simple stack). I checked that the fix from comment #3 is present. How can I see heat events?
Udi, do you have this configuration in your /etc/heat/heat.conf ? notification_driver=messaging notification_topics=notifications
I was able to catch heat events in the timelines after adjusting the haproxy config with section for exposing rabbitmq overs the external VIP. Also the cloud provider needs the amqp server credentials during registration for this to work.
Created attachment 1167828 [details] Timelines screenshot Attaching the Timelines screenshot.
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. https://access.redhat.com/errata/RHBA-2016:1348