Description of problem: If RabbitMQ is used, DEBUG enabled components write excessive time out messages like, ~~~ DEBUG oslo.messaging._drivers.impl_rabbit [-] Timed out waiting for RPC response: timed out _raise_timeout /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:1049 DEBUG oslo.messaging._drivers.impl_rabbit [-] Timed out waiting for RPC response: Timeout while waiting on RPC response - topic: "<unknown>", RPC method: "<unknown>" info: "<unknown>" _raise_timeout /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:1049 ~~~ Version-Release number of selected component (if applicable): current python-oslo-messaging How reproducible: Always Steps to Reproduce: 1. Enable DEBUG option in nova, neutron. 2. Restart nova, neutron package. 3. Observe whether the messages is shown. Actual results: Too many messages are written to logs. Expected results: The message should be surpress. Additional info: Upstream LP and gerrit are below. LP: https://bugs.launchpad.net/oslo.messaging/+bug/1714558 Gerrit: https://review.openstack.org/#/c/500210/
The package python-oslo-messaging-5.10.2-2.el7ost is now ready for tests!
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:2671