kolla

rabbitmq is not binding to a single address

Bug #1478073 reported by Sam Yaple
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Critical
Sam Yaple
kolla liberty-2 "liberty-2"

Bug Description

rabbitmq currently binds to all available addresses. This will not work for multinode where haproxy also lives on a box with rabbitmq and is just bad practice in my opinion

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/205612

Changed in kolla:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/205612
Committed: https://git.openstack.org/cgit/stackforge/kolla/commit/?id=0c6594c25864d0c90cd0009726cee84967fe65dc
Submitter: Jenkins
Branch: master

commit 0c6594c25864d0c90cd0009726cee84967fe65dc
Author: Sam Yaple <email address hidden>
Date: Fri Jul 24 16:18:08 2015 +0000

    Tells rabbitmq to listen on single ip

    This binds rabbitmq, epmd, and the management plugin to a single ip. The
    syntax is very tricky, but this is all functional.

    Change-Id: Iecbb00f6c4fe3044688ae3258da31b9aabbd1501
    Closes-Bug: #1478073

Changed in kolla:
status: In Progress → Fix Committed
Sam Yaple (s8m)
Changed in kolla:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.