Bug 1538058
Summary: | [RFE] RabbitMQ durable queues lead to fail of event handler for OpenStack AMQP | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Neha Chugh <nchugh> |
Component: | Providers | Assignee: | Scott Seago <sseago> |
Status: | CLOSED ERRATA | QA Contact: | Danylo Kholodov <dkholodo> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.9.0 | CC: | akarol, dkholodo, gblomqui, igortiunov, jfrey, jhardy, obarenbo, simaishi, slucidi, smallamp, sseago |
Target Milestone: | GA | Keywords: | FutureFeature |
Target Release: | 5.10.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | 5.10.0.15 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-07 23:01:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Feature | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | Openstack | Target Upstream Version: | |
Embargoed: |
Description
Neha Chugh
2018-01-24 11:56:54 UTC
Sending to PM for prioritization. New commit detected on ManageIQ/manageiq-providers-openstack/master: https://github.com/ManageIQ/manageiq-providers-openstack/commit/fd6cc79deeda0007af1275f4cd9d1464e0c33cee commit fd6cc79deeda0007af1275f4cd9d1464e0c33cee Author: Scott Seago <sseago> AuthorDate: Mon Sep 10 11:23:51 2018 -0400 Commit: Scott Seago <sseago> CommitDate: Mon Sep 10 11:23:51 2018 -0400 bug 1538058: Retry bunny queue initialization for durable queues https://bugzilla.redhat.com/show_bug.cgi?id=1538058 If rabbitmq is using durable queue/exchanges, they must be opened on the ManageIQ end with durable => true. If exchange creation fails with Bunny::PreconditionFailed, retry with durable=>true. lib/manageiq/providers/openstack/legacy/events/openstack_rabbit_event_monitor.rb | 30 +- 1 file changed, 24 insertions(+), 6 deletions(-) Danylo, Regarding your first question, there's actually nothing that needs to be done to enable this. If connecting to the queue fails because it is durable, CFME tries again setting the durable flag to 'true'. Regarding the second, I'm not quite sure I understand what you're asking. "use CFME in some way" -- if the durable queue already exists, without this fix, trying to use AMQP messaging with the provider will fail since the attempt to create/connect to a non-durable queue will fail because the queue already exists as a durable one. With this fix, using AMQP will succeed. Perhaps, before testing this fix, make sure that you're setting up the durable queue properly by confirming that using AMQP fails for you if you are using a build without this fix. Then, if that fails, it should succeed with the fix in place. Verified at the CFME 5.10.0.29 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/RHSA-2019:0212 |