Attempted access a driver-specific msg_id field

Bug #1855775 reported by Ken Giusti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Fix Committed
High
Ken Giusti

Bug Description

The RPC server operates on an abstract class that represents an incoming message (RPCIncomingMessage). Message bus drivers are allowed to extend this class, but the generic RPC server and client code must only access the RPCIncomingMessage interface.

A patch [1] that added extra message tracing violated that and accessed an attribute that was only available to the rabbitmq incoming message derived class (msg_id).

This will cause servers using a non-rabbitmq driver to fail on RPC request arrival.

[1] https://bugs.launchpad.net/oslo.messaging/+bug/1847747

Revision history for this message
Ken Giusti (kgiusti) wrote :

Oopsie - forgot to reference the review link:
https://review.opendev.org/#/c/698090/

Changed in oslo.messaging:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Ken Giusti (kgiusti)
Ken Giusti (kgiusti)
Changed in oslo.messaging:
status: Fix Committed → In Progress
status: In Progress → Fix Committed
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.