Bug 1538956
Summary: | instances lost network connectivity after live migration | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Eduard Barrera <ebarrera> |
Component: | rabbitmq-server | Assignee: | Peter Lemenkov <plemenko> |
Status: | CLOSED ERRATA | QA Contact: | Udi Shkalim <ushkalim> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 11.0 (Ocata) | CC: | abeekhof, amuller, apevec, chjones, chrisw, ebarrera, jamsmith, jeckersb, jlibosva, lhh, mkrcmari, nyechiel, plemenko, ragiman, srevivo, vkommadi |
Target Milestone: | z3 | Keywords: | Triaged, ZStream |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rabbitmq-server-3.6.5-7.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-08-20 12:53:41 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
Eduard Barrera
2018-01-26 09:01:28 UTC
Neutrons RPC calls are failing as its connection to AMQP server is broken. May be rabbit dfg can look into why clients are losing connection to AMQP server. Hello All. I'm still investigating this, but let me do an intermediate report. I've found an issue in between 16-Jan-2018::18:28:30 and 16-Jan-2018::18:28:36 which looks like another reincarnation of a https://github.com/rabbitmq/rabbitmq-server/issues/687. * RabbitMQ at pollux-controller-2 died (18:30). * RabbitMQ at pollux-controller-1 received a single ack for some message. * Unfortunately its queue of unacked messages is empty (unhandled situation) * RabbitMQ at pollux-controller-1 dies abruptly * RabbitMQ at pollux-controller-2 rebooted (18:36). * It happens during unhealthy cluster state As for situation mentioned above (~ 16-Jan-2018::14:30). Indeed there was some networking glitch. However none of RabbitMQ nodes lost connectivity to each other, and their restored accepting connections since 16-Jan-2018::14:45. I can't explain this one, but it looks like something which has external (to RabbitMQ) cause. I'm looking into this. This build (rabbitmq-server-3.6.5-7.el7ost) should fix all RabbitMQ-specific issues found in mentioned customer's cases. 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. https://access.redhat.com/errata/RHBA-2018:2521 |