[messaging] QpidMessage constructor incorrectly called

Bug #1282787 reported by Ken Giusti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
oslo.messaging
In Progress
Undecided
Rafael Folco

Bug Description

See:

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

The consume() method fails to call the QpidMessage constructor properly - the session argument is missing:

(04:11:31 PM) ttracy: ERROR:oslo.messaging._drivers.impl_qpid:Failed to process message... skipping it.
(04:11:33 PM) ttracy: Traceback (most recent call last):
(04:11:35 PM) ttracy: File "/usr/lib/python2.6/site-packages/oslo/messaging/_drivers/impl_qpid.py", line 197, in consume
(04:11:37 PM) ttracy: self.callback(QpidMessage(message))
(04:11:39 PM) ttracy: TypeError: __init__() takes exactly 3 arguments (2 given)

Revision history for this message
Arx Cruz (arxcruz) wrote :

I can confirm this is affecting devstack with qpid.

Changed in oslo.messaging:
status: New → Confirmed
Changed in oslo.messaging:
assignee: nobody → Rafael Folco (rafaelfolco)
status: Confirmed → In Progress
Revision history for this message
Rafael Folco (rafaelfolco) wrote :

Submitted a patch to address this issue:
https://review.openstack.org/#/c/75413

Revision history for this message
Arx Cruz (arxcruz) wrote :

I would like that the Project maintainer assign this bug as High Priority. It's an easy one to resolve, and it's blocking us to start report back to Openstack-infra community, since in our environment, the only MQ available is the qpid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.