Description of problem: Sometimes when a controller is rebooted the node is unable to join the rabbitmq cluster. This issue needs the following to happen to be fixed: 1) BZ https://bugzilla.redhat.com/show_bug.cgi?id=1247303 needs a fix in the resource agent (see this BZ for more history about this issue) 2) We need to add the meta parameter "notify=true" on fresh installs and on updates. Note, that if the fix to THT makes it in before the fix of the resource agent, nothing happens (i.e. things keep going like before)
openstack-tripleo-heat-templates-0.8.10-2.el7ost [root@overcloud-controller-0 heat-admin]# pcs resource show rabbitmq Resource: rabbitmq (class=ocf provider=heartbeat type=rabbitmq-cluster) Attributes: set_policy="ha-all ^(?!amq\.).* {"ha-mode":"all"}" Meta Attrs: notify=true Operations: start interval=0s timeout=100 (rabbitmq-start-interval-0s) stop interval=0s timeout=90 (rabbitmq-stop-interval-0s) monitor interval=10 timeout=40 (rabbitmq-monitor-interval-10) [root@overcloud-controller-0 heat-admin]#
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-0604.html