From 71d72ed081034ec123fa152da4d5000bbb1d4cf5 Mon Sep 17 00:00:00 2001 From: Vladislav Belogrudov Date: Thu, 2 Nov 2017 17:01:29 +0300 Subject: [PATCH] Murano application should contact rabbitmq by external FQDN In case of external router internal VIP and external VIP are the same. External router manages port/address redirection from public network to OpenStack API. The address of the router is set via 'kolla_external_fqdn'. Currently Murano configuration that is handed over to Murano application instance uses 'kolla_external_vip_address'. This leads to the instance trying to connect to internal API network. Correct address should be 'kolla_external_fqdn' which will work in both cases - either with double VIP setup or with single VIP + external router. Change-Id: I78c38ae0af1cecd2be2b1c6cc86bcfc51b847082 Closes-Bug: #1729611 --- ansible/roles/murano/templates/murano.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ansible/roles/murano/templates/murano.conf.j2 b/ansible/roles/murano/templates/murano.conf.j2 index 4dc06648cc..98f85e3e43 100644 --- a/ansible/roles/murano/templates/murano.conf.j2 +++ b/ansible/roles/murano/templates/murano.conf.j2 @@ -42,7 +42,7 @@ driver = messagingv2 {% if service_name == 'murano-engine' %} [rabbitmq] -host = {{ kolla_external_vip_address }} +host = {{ kolla_external_fqdn }} port = {{ outward_rabbitmq_port }} login = {{ murano_agent_rabbitmq_user }} password = {{ murano_agent_rabbitmq_password }}