Cleanly exit the call monitor thread if the reply send fails

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

Bug Description

It is possible to fail sending the heartbeat during call monitoring. This can raise an internal exception (AMQPDestinationNotFound) should the broker restart.

Currently the heartbeat routine does not handle any exceptions. It should simply log a message and exit the monitor thread (leaving the RPC call to timeout which is expected in this case).

Ken Giusti (kgiusti)
Changed in oslo.messaging:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ken Giusti (kgiusti)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

Fix proposed to branch: master
Review: https://review.openstack.org/638248

Changed in oslo.messaging:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (master)

Reviewed: https://review.opendev.org/638248
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=f948e24294dfb7dfa1342d64da749c3adeb5e2e5
Submitter: Zuul
Branch: master

commit f948e24294dfb7dfa1342d64da749c3adeb5e2e5
Author: Kenneth Giusti <email address hidden>
Date: Wed Feb 20 12:08:04 2019 -0500

    Handle unexpected failures during call monitor heartbeat

    Change-Id: Iec04c18ac3565a3610377d94caf128c6704a89eb
    Closes-Bug: #1816816

Changed in oslo.messaging:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.messaging 9.7.0

This issue was fixed in the openstack/oslo.messaging 9.7.0 release.

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.