+++ 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.
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
This was backported to grizzly here: https://review.openstack.org/#/c/68880/
> https://review.openstack.org/#/c/68880/ This was included in 2013.1.5
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.
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