From 961eb7a9896fc2ea9bbeea70b6ccde20b5d92a8a Mon Sep 17 00:00:00 2001
From: OlgaGusarenko <ogusarenko@mirantis.com>
Date: Fri, 26 Jun 2015 13:23:21 +0300
Subject: [PATCH] [MU4] Oslo.Messaging issue fixed

Adds possible usage of undefined variable in oslo.messaging resolved
issue.

Change-Id: Icf2926e74329aa2f5b5b7db0cb74b00678e38d6d
---
 .../release-notes/v6-0/updates/9010-others.rst  | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/pages/release-notes/v6-0/updates/9010-others.rst b/pages/release-notes/v6-0/updates/9010-others.rst
index d89ca1e61..89cf6bcf3 100644
--- a/pages/release-notes/v6-0/updates/9010-others.rst
+++ b/pages/release-notes/v6-0/updates/9010-others.rst
@@ -22,6 +22,23 @@ Resolved Issues
 * The memory leak in python-libvirt that affected Compute service
   has been fixed. See `LP1419362 <https://bugs.launchpad.net/mos/6.0-updates/+bug/1419362>`_.
 
+
+Oslo.Messaging
+--------------
+
+Resolved Issues
++++++++++++++++
+
+* In the ``reconnect()`` method, a variable was defined after it had been
+  used in the ``if`` section. This could lead to an unpredictable behavior
+  while getting timeout exception on connection. The varaiable definition
+  in ``Connection.reconnect()`` has been fixed.
+  See `LP1465300 <https://bugs.launchpad.net/mos/+bug/1465300>`_.
+
+* Now, in case of restarting RabbitMQ during rpc-call
+  ``oslo.messaging``, RPC does not get stuck doing infinite connection
+  retries anymore. See `LP1457055 <https://bugs.launchpad.net/mos/+bug/1457055>`_.
+
 Other Resolved Issues
 ---------------------