Red Hat Bugzilla – Bug 1290538
Oslo messaging always connecting to the frist configured rabbitmq broker
Last modified: 2016-04-18 02:54:45 EDT
Description of problem:
What problem/issue/behavior are you having trouble with? What do you expect to see?
Openstack services always connect to the first message broker defined in the rabbit_hosts list.
This issue was solved in Icehouse but was introduced again during the refactor done here:
This issue impacts in the load balancing of rabbitmq connections and introduces a degradation of the service when the first controller is down (as Oslo always try to connect to the Stopped broker, and after the failure, it connects to the second one)
The patch has been submitted upstream:
We would like to backport it downstream as soon as possible
Version-Release number of selected component (if applicable):
*** This bug has been marked as a duplicate of bug 1267736 ***