Description of problem: RabbitMQ instances running at overcloud can be accessed by anyone who knows their ips with the default RabbitMQ credentials Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-0.8.6-46.el7ost.noarch
*** Bug 1265808 has been marked as a duplicate of this bug. ***
Hi Giulio, How can we verify this one? any steps to reproduce? Thanks
hi Udi, you should be able to customize both the default RabbitMQ username and password by providing the following two params (merged into a custom environment file passed with -e at deployment time): parameter_defaults: RabbitUserName: myuser RabbitPassword: mypassword those values should get reflected into the rabbitmq.config file (on the controller nodes) and into the various openstack services config file
Thanks Giulio Verified on ospd 7.2 openstack-tripleo-heat-templates-0.8.6-87.el7ost.noarch Deploy command: openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --ntp-server 10.11.160.238 --timeout 90 -e /home/stack/rabbit.yaml [stack@instack ~]$ cat rabbit.yaml parameter_defaults: RabbitUserName: "foo" RabbitPassword: "bar" Deployment Passed successfully [root@overcloud-controller-0 ~]# rabbitmqctl list_permissions Listing permissions in vhost "/" ... foo .* .* .* ...done.
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-2015:2650