Bug 1121185
Summary: | When using rabbitmq AMQP traffic should be load balanced accross all nodes | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Steve Reichard <sreichar> |
Component: | openstack-foreman-installer | Assignee: | John Eckersberg <jeckersb> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 (RHEL 7) | CC: | jeckersb, jguiditt, mburns, morazi, rhos-maint, sreichar, yeylon |
Target Milestone: | ga | ||
Target Release: | Installer | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-foreman-installer-2.0.17-1.el6ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 18:05:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steve Reichard
2014-07-18 15:07:16 UTC
Steve, sanity check me since I am an haproxy newbie. I should just need to remove these two lines to achieve the expected behavior, correct? stick on dst stick-table type ip size 2 That was my understanding but more importantly this agrees with what Ryan O'Hara e-mailed me: Just take out the 'stick on dst' and the 'stick-table type ip size 2' and you're good. Ryan openstack-foreman-installer-2.0.17-1.el6ost listen amqp bind 192.168.0.99:5672 mode tcp option tcplog timeout client 120s timeout server 120s server mac047d7b627d5a.example.com 192.168.0.2:5672 check inter 1s server mac047d7b685a04.example.com 192.168.0.5:5672 check inter 1s server mac047d7b61754e.example.com 192.168.0.3:5672 check inter 1s stick on dst stick-table type ip size 2 were removed. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html |