Rabbit "guest from everywhere" should be reverted

Bug #1317778 reported by jan grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Unassigned

Bug Description

When the work on

https://bugs.launchpad.net/tripleo/+bug/1315474

to add user accounts for all rabbit consumers is complete, then the patch

https://review.openstack.org/#/c/92815/ (Permit non-loopback guest access to Rabbit) should be reverted.

Triage: Should be raised at high priority as an aide memoire.

Ben Nemec (bnemec)
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-image-elements (master)

Reviewed: https://review.openstack.org/92815
Committed: https://git.openstack.org/cgit/openstack/tripleo-image-elements/commit/?id=537a440cd00c7fbbd641fe13eec693b500dbb89c
Submitter: Jenkins
Branch: master

commit 537a440cd00c7fbbd641fe13eec693b500dbb89c
Author: Jan Grant <email address hidden>
Date: Thu May 8 13:00:22 2014 +0100

    Permit non-loopback guest access to Rabbit.

    Recent versions of RabbitMQ have defaulted to only permitting the guest
    user to connect from the loopback address.

    Many elements have yet to consume rabbit accounts - until the configuration
    of per-service (or per-server) accounts is finalised, ensure that newer
    rabbit versions will be backwardly-compatible with the old behaviour.

    Change-Id: I30e0156862c5672aef3e31a6919c8fe1957e3a02
    Related-bug: #1315474
    Related-bug: #1317778

Changed in tripleo:
status: Triaged → Fix Released
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.