Description of problem:
RabbitMQ url is incorrectly set in proxy-server.conf when deploying composable roles.
Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-5.0.0-0.9.0rc3.el7ost.noarch
How reproducible:
100%
Steps to Reproduce:
1. Deploy overcloud
source ~/stackrc
export THT=/usr/share/openstack-tripleo-heat-templates/
openstack overcloud deploy --templates $THT \
-r ~/openstack_deployment/roles/roles_data.yaml \
-e $THT/environments/network-isolation.yaml \
-e $THT/environments/network-management.yaml \
-e $THT/environments/storage-environment.yaml \
-e $THT/environments/tls-endpoints-public-ip.yaml \
-e ~/openstack_deployment/environments/nodes.yaml \
-e ~/openstack_deployment/environments/network-environment.yaml \
-e ~/openstack_deployment/environments/disk-layout.yaml \
-e ~/openstack_deployment/environments/public_vip.yaml \
-e ~/openstack_deployment/environments/enable-tls.yaml \
-e ~/openstack_deployment/environments/inject-trust-anchor.yaml \
-e ~/openstack_deployment/environments/scheduler_hints_env.yaml \
-e ~/openstack_deployment/environments/ips-from-pool-all.yaml \
-e ~/openstack_deployment/environments/neutron-settings.yaml \
--log-file overcloud_deployment.log &> overcloud_install.log
Actual results:
/etc/swift/proxy-server.conf on the ServiceApi role nodes gets configured with the ip address of the local node instead of the ip addresses of the controller nodes where the rabbitmq services is running:
[root@api-r01-01 ~]# grep rabbit /etc/swift/proxy-server.conf
url = rabbit://guest:GtnJqaPQzNR8udmX29fe3XKAP.0.14:5672//
[root@api-r01-01 ~]# ip a | grep 10.0.0.14
inet 10.0.0.14/25 brd 10.0.0.127 scope global vlan200
[root@api-r01-01 ~]# grep '10.0.0.14 ' /etc/hosts
10.0.0.14 api-r01-01.redhat.local api-r01-01
10.0.0.14 api-r01-01.internalapi.redhat.local api-r01-01.internalapi
Expected results:
The rabbitmq url contains the IP addresses of the controller nodes where the rabbitmq service is binding.
Additional info:
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://rhn.redhat.com/errata/RHEA-2016-2948.html