[Bug 1436788] Fix included in openstack/oslo.messaging 1.8.3

[OpenStack Infra]

This issue was fixed in the openstack/oslo.messaging 1.8.3 release.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1436788

Title:
  rabbitmq heartbeat failures don't reset connections

Status in oslo.messaging:
  Fix Released
Status in oslo.messaging package in Ubuntu:
  Fix Released
Status in oslo.messaging source package in Vivid:
  Fix Released

Bug description:
  Testing with oslo.messaging 1.8.1 and kilo-3 of OpenStack; three node
  rabbitmq cluster, native rabbitmq clustering, no haproxy!

  Restarting the rabbitmq brokers cleanly works just fine, connections
  switch to a different broker and all is good in the world.

  However, if I yank a broker off the network uncleanly, clients
  connections detect the missed heartbeats, but don't reset connections
  and switch to a new broker until the system tcp timeout is reached.

  See attached log files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1436788/+subscriptions