From 5480bd9b1d3a9efcd3618ddf12718d2621ceeb47 Mon Sep 17 00:00:00 2001 From: Jeffrey Zhang Date: Wed, 14 Sep 2016 09:52:38 +0800 Subject: [PATCH] Bind EPMD to api interface address Closes-Bug: #1562701 Change-Id: Ica68bdee81223232995bc21ad5e5d5fbf9e8b05f --- ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 b/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 index 55eaab9d80..81ccce679d 100644 --- a/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 +++ b/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2 @@ -6,14 +6,5 @@ RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS="-pa /usr/lib/rabbitmq/lib/{{ rabbitmq_versi RABBITMQ_LOG_BASE=/var/log/kolla/rabbitmq -# TODO(sdake, vhosakot) -# erlang by default binds to wildcard (all interfaces) and can potentially -# interfere with the neutron external or tenant networks. We should in theory -# bind epmd to the host's IPv4 address to address the issue however this also -# has issues and can crash erlang when it is compiled with IPv6 support. -# See bugs: -# https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1374109 -# https://bugs.launchpad.net/kolla/+bug/1562701 -# https://bugzilla.redhat.com/show_bug.cgi?id=1324922 - +export ERL_EPMD_ADDRESS={{ api_interface_address }} export ERL_EPMD_PORT={{ rabbitmq_epmd_port }}