Actions
Bug #61639
closedamqp: notifications are not retired on persistent topic
% Done:
0%
Source:
Community (user)
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v18.0.0-4599-ga20a4d95b90
Released In:
v19.2.0~2106
Upkeep Timestamp:
2025-07-12T07:38:48+00:00
Description
if the broker goes down, notifications are not sent when the broker recovers
Updated by Yuval Lifshitz almost 3 years ago
was not able to reproduce the issue, following these steps: https://gist.github.com/yuvalif/e58e264bafe847bc5196f95be0e704a2
however, race conditions similar to the ones found in kafka may happen in amqp as well
Updated by Yuval Lifshitz almost 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 52110
Updated by Casey Bodley over 2 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to pacific quincy reef
Updated by Upkeep Bot over 2 years ago
- Copied to Backport #61918: pacific: amqp: notifications are not retired on persistent topic added
Updated by Upkeep Bot over 2 years ago
- Copied to Backport #61919: reef: amqp: notifications are not retired on persistent topic added
Updated by Upkeep Bot over 2 years ago
- Copied to Backport #61920: quincy: amqp: notifications are not retired on persistent topic added
Updated by Casey Bodley over 2 years ago
- Related to Bug #62264: [ FAILED ] TestAMQP.IdleConnection (30132 ms) added
Updated by Casey Bodley over 2 years ago
@Yuval this is a high-priority bug fix that hasn't been backported to quincy or pacific
Updated by Yuval Lifshitz about 1 year ago
- Status changed from Pending Backport to Resolved
Updated by Upkeep Bot 8 months ago
- Merge Commit set to a20a4d95b9009d80652c4430460388dccc0c4c14
- Fixed In set to v18.0.0-4599-ga20a4d95b90
- Released In set to v19.2.0~2106
- Upkeep Timestamp set to 2025-07-12T07:38:48+00:00
Actions