Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1600960

Summary:	[OSP12] Backport of Suppress excessive debug logs when consume rabbit in oslo-messaging
Product:	Red Hat OpenStack	Reporter:	Victor Stinner <vstinner>
Component:	python-oslo-messaging	Assignee:	Hervé Beraud <hberaud>
Status:	CLOSED ERRATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	aherr, amcleod, apevec, chjones, dcadzow, fpercoco, jeckersb, knoha, lhh, michele, mkrcmari, pkomarov, srevivo, ushkalim, vstinner
Target Milestone:	---	Keywords:	FeatureBackport, Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-oslo-messaging-5.30.4-1.el7ost	Doc Type:	Enhancement
Doc Text:	Previously, when an OpenStack service logs at DEBUG level, Oslo Messaging logs the message "Timed out waiting for RPC response" unnecessarily. With this fix, Oslo Messaging no longer logs this message in instances when the timeout is recoverable.	Story Points:	---
Clone Of:	1599975	Environment:
Last Closed:	2018-12-05 18:54:06 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:
Bug Depends On:	1599975
Bug Blocks:

Comment 2 Victor Stinner 2018-07-13 13:30:08 UTC

I backported the change upstream: https://review.openstack.org/#/c/582542/

Comment 4 Victor Stinner 2018-08-27 08:20:32 UTC

Oslo Messaging 5.30.4 has been released with the fix.

Comment 5 Victor Stinner 2018-09-28 12:12:43 UTC

The python-oslo-messaging-5.30.4-1.el7ost package is now ready for QA.

Comment 15 errata-xmlrpc 2018-12-05 18:54:06 UTC

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:3790