RabbitMQ should not install when not needed

Bug #1513132 reported by Tom Cameron
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Low
Major Hayden

Bug Description

When deploying with OSA, RabbitMQ should only install if it is depended on by another play. An example would be a SWIFT-only deployment.

Currently, this is causing an issue with the rpc-openstack monitoring components because Rabbit's server process is running there are no channels configured.

Revision history for this message
Kevin Carter (kevin-carter) wrote :

After a brief conversation in the channel it was determined that we can do most of this with affinity settings. We've decided that the best fix at this time would be to add additional documentation on how the affinity groups work and can be customized.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
Changed in openstack-ansible:
assignee: nobody → Major Hayden (rackerhacker)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)

Fix proposed to branch: master
Review: https://review.openstack.org/258116

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

Reviewed: https://review.openstack.org/258116
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=a09fc0edeea0e6500c3f842bd3664c228e8fa2fc
Submitter: Jenkins
Branch: master

commit a09fc0edeea0e6500c3f842bd3664c228e8fa2fc
Author: Major Hayden <email address hidden>
Date: Tue Dec 15 13:09:33 2015 -0600

    Adding docs for affinity

    This documentation explains affinity and also tells users how to avoid
    deploying RabbitMQ containers for standalone swift deployments.

    Closes-Bug: 1513132

    Change-Id: Id94a14ebb9d97f0714ed63131e60fa6c13094719

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (liberty)

Fix proposed to branch: liberty
Review: https://review.openstack.org/258500

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (kilo)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (kilo)

Reviewed: https://review.openstack.org/258501
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=a9fc5f589fa98c938239709dc76dcbe17126bab0
Submitter: Jenkins
Branch: kilo

commit a9fc5f589fa98c938239709dc76dcbe17126bab0
Author: Major Hayden <email address hidden>
Date: Tue Dec 15 13:09:33 2015 -0600

    Adding docs for affinity

    This documentation explains affinity and also tells users how to avoid
    deploying RabbitMQ containers for standalone swift deployments.

    Closes-Bug: 1513132

    Change-Id: Id94a14ebb9d97f0714ed63131e60fa6c13094719
    (cherry picked from commit a09fc0edeea0e6500c3f842bd3664c228e8fa2fc)

tags: added: in-kilo
tags: added: in-liberty
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (liberty)

Reviewed: https://review.openstack.org/258500
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=37a7c95f51f81bbac2597a7295a20e1cd52b13d5
Submitter: Jenkins
Branch: liberty

commit 37a7c95f51f81bbac2597a7295a20e1cd52b13d5
Author: Major Hayden <email address hidden>
Date: Tue Dec 15 13:09:33 2015 -0600

    Adding docs for affinity

    This documentation explains affinity and also tells users how to avoid
    deploying RabbitMQ containers for standalone swift deployments.

    Closes-Bug: 1513132

    Change-Id: Id94a14ebb9d97f0714ed63131e60fa6c13094719
    (cherry picked from commit a09fc0edeea0e6500c3f842bd3664c228e8fa2fc)

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 12.0.8

This issue was fixed in the openstack/openstack-ansible 12.0.8 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
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.9

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

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

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

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

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

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

This issue was fixed in the openstack/openstack-ansible 12.0.11 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.

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

This issue was fixed in the openstack/openstack-ansible 11.2.15 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.