Bug 1351547
Summary: | Rabbitmq clone starts on just one node in a HA deploy | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | Raoul Scarazzini <rscarazz> |
Component: | openstack-tripleo | Assignee: | James Slagle <jslagle> |
Status: | CLOSED UPSTREAM | QA Contact: | Shai Revivo <srevivo> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | trunk | CC: | chris.brown, jschluet, plemenko, rscarazz |
Target Milestone: | --- | ||
Target Release: | trunk | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-18 11:47:26 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
Raoul Scarazzini
2016-06-30 10:03:03 UTC
SOS reports for all the controllers: http://file.rdu.redhat.com/rscarazz/BZ1351547/ I also tried a clean startup after removing all the stalled data inside /var/lib/rabbitmq/mnesia, but it did not helped. From what I see iptables blocks TCP connections between nodes on port 4369. This prevents rabbitmq cluster from assembling. Maybe there are some other issues. I confirm the connection problem is due to an iptables rule missing. Doing these steps on each controller: sudo sed -i -e 's/--dports 5672,35672/--dports 4369,5672,35672/g' /etc/sysconfig/iptables sudo systemctl restart iptables And then cleaning up rabbitmq-clone on one of the three controller: sudo pcs resource cleanup rabbitmq-clone solves the problem. An upstream patch [1] was submitted to solve this problem and should be merged quickly. [1] https://review.openstack.org/#/c/336072/ Fixed was merged upstream so closing. |