Rabbit config changes dont initiate a restart

[Andy McCrae]

At present we can make changes to rabbitmq config files which require a restart to be used, but the restart isnt initiated.

Following on from the discussions here:
https://review.openstack.org/#/c/186243/

Rabbit cluster restarting could be complicating, although it might be worth just restarting simultaneously across rabbit servers and acknowledging that you could lose a few messages.

[Jesse Pretorius (jesse-pretorius)]

There's some detail in the clustering guide about restarting cluster nodes: https://www.rabbitmq.com/clustering.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: kilo
Review: https://review.openstack.org/198193

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/198193
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=c0676ba066077d47f3432b0b7ea2749db36e0c71
Submitter: Jenkins
Branch: kilo

commit c0676ba066077d47f3432b0b7ea2749db36e0c71
Author: Tom Cameron <email address hidden>
Date: Thu Jul 2 17:21:13 2015 -0400

    Rabbit config changes dont initiate a restart

    Restart rabbit-server when the config files change. This required
    the templates to be rendered from the post_install playbook to
    prevent attempting to restart a service that had not yet been
    installed.

    Change-Id: I7c9ba030aa0e58d3fb5fa3cb6f17dd013f36471c
    Closes-Bug: #1460115
    (cherry picked from commit 90bef6a3c47580aaf99b81c6842404e027e01924)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.