[MU4] Oslo.Messaging issue fixed

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

Change-Id: Icf2926e74329aa2f5b5b7db0cb74b00678e38d6d
This commit is contained in:
OlgaGusarenko
2015-06-26 13:23:21 +03:00
committed by Olena Logvinova
parent 41a3bbfa40
commit 961eb7a989

View File

@@ -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
---------------------