Bug 1050214 – Thread consuming qpid messages can die silently

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1050214 - Thread consuming qpid messages can die silently

Summary:	Thread consuming qpid messages can die silently

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-quantum (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	z5
Target Release:	3.0
Assigned To:	Miguel Angel Ajo
QA Contact:	Lon Hohberger
Docs Contact:

URL:
Whiteboard:
Keywords:	OtherQA, Rebase, ZStream

Depends On:	1050213 1050215 1050216 1050217 1054246
Blocks:
	Show dependency tree / graph

Reported:	2014-01-08 16:04 EST by Russell Bryant
Modified:	2016-04-26 09:31 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	openstack-quantum-2013.1.5-1.el6ost
Doc Type:	Bug Fix
Doc Text:	Cause: The thread loop processing RPC could die because of an unexpected exception in the code. Consequence: When an unexpected exception happened, the agent / server processing those handling any more RPC calls. Fix: The RPC look captures and logs unexpected exceptions without crashing. Result: Exceptions will be logged, RPC won't stop working when that occurs.
Story Points:	---
Clone Of:	1050213
Clones:	1054249 (view as bug list)
Environment:
Last Closed:	2014-04-03 14:17:05 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1189711	None	None	None	Never
Red Hat Product Errata	RHBA-2014:0363	normal	SHIPPED_LIVE	Red Hat Enterprise Linux OpenStack Platform 3 Bug Fix and Enhancement Advisory	2014-04-03 18:16:48 EDT

Groups: None (edit)

Description Russell Bryant 2014-01-08 16:04:12 EST

+++ This bug was initially created as a clone of Bug #1050213 +++

The code for receiving and processing qpid messages runs in its own greenthread.  Unfortunately, there is a code path that if it raises an exception, the greenthread will die silently, without any entry in the log file.

In particular, the code in question is:

https://git.openstack.org/cgit/openstack/nova/tree/nova/openstack/common/rpc/impl_qpid.py?h=stable/grizzly#n468

if self.session.next_receiver() raises an exception other than qpid's Empty or ConnectionError exceptions, the thread will die and no more messages will be received.

The fix is to backport the portion of the following change that applies to impl_qpid.  That includes the new decorator in excutils and the change to impl_qpid.py.

Comment 1 Russell Bryant 2014-01-08 16:12:17 EST

The change that needs to be backported is: https://review.openstack.org/#/c/32235/13

I also attached a version of the backport for nova to bug 1050213

Comment 5 Miguel Angel Ajo 2014-02-18 07:59:06 EST

This was backported to grizzly here:

https://review.openstack.org/#/c/68880/

Comment 6 Alan Pevec 2014-03-27 22:26:30 EDT

> https://review.openstack.org/#/c/68880/

This was included in 2013.1.5

Comment 9 Lon Hohberger 2014-04-01 10:18:18 EDT

I verified that the patch was incorporated in the 2013.1.5 rebase and that the openstack-quantum package passed basic sanity checks by running various administrative commands and booting a virtual machine which utilized it for network services.

Comment 11 errata-xmlrpc 2014-04-03 14:17:05 EDT

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.

http://rhn.redhat.com/errata/RHBA-2014-0363.html

Note You need to log in before you can comment on or make changes to this bug.