The scenario: scale compute-node (N->N+1) -> check that rabbit-service is still running worked well on my environment with director 9.0 puddle - 2016-05-26.1. [root@overcloud-controller-1 ~]# rpm -qa | grep rabbit rabbitmq-server-3.6.2-3.el7ost.noarch post-scale: ------------- Scale Command : openstack overcloud deploy --templates --control-scale 3 --compute-scale 2 --ceph-storage-scale 2 --neutron-network-type vxlan --neutron-tunnel-types vxlan --ntp-server 10.5.26.10 --timeout 90 -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml Stack overcloud UPDATE_COMPLETE Overcloud Endpoint: http://10.19.184.210:5000/v2.0 Overcloud Deployed 27- Started: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 ] 28: Clone Set: rabbitmq-clone [rabbitmq] 29- Started: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2
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-1597.html