Rabbit "guest from everywhere" should be reverted
Bug #1317778 reported by
jan grant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
When the work on
https:/
to add user accounts for all rabbit consumers is complete, then the patch
https:/
Triage: Should be raised at high priority as an aide memoire.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/92815 /git.openstack. org/cgit/ openstack/ tripleo- image-elements/ commit/ ?id=537a440cd00 c7fbbd641fe13ee c693b500dbb89c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 537a440cd00c7fb bd641fe13eec693 b500dbb89c
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 compatible with the old behaviour.
of per-service (or per-server) accounts is finalised, ensure that newer
rabbit versions will be backwardly-
Change-Id: I30e0156862c567 2aef3e31a6919c8 fe1957e3a02
Related-bug: #1315474
Related-bug: #1317778