Rabbit config changes dont initiate a restart

Bug #1460115 reported by Andy McCrae
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Medium
Tom Cameron

Bug Description

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.

Tags: in-kilo
Changed in openstack-ansible:
milestone: none → 11.0.3
Changed in openstack-ansible:
milestone: 11.0.3 → 11.0.4
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

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

Changed in openstack-ansible:
assignee: Andy McCrae (andrew-mccrae) → Tom Cameron (tom-cameron)
Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

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

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

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)

tags: added: in-kilo
Changed in openstack-ansible:
status: Fix Committed → Fix Released
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

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

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

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

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.