The [oslo_messaging_notification]retry parameter is not applied during
connecting to the message bus. But the documentation implies it should[1][2].
The two possible drivers, rabbit and kafka, behaves differently.
1) The rabbit driver will retry the connection forever, blocking the caller
process.
2) The kafka driver also ignores the retry configuration but the
notifier call returns immediately even if the notification is not
(cannot) be delivered.
This patch adds test cases to show the wrong behavior.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.messaging /+/828868 /opendev. org/openstack/ oslo.messaging/ commit/ d63173a31f50025 4277641a76bb721 a8bf07ad9c
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit d63173a31f50025 4277641a76bb721 a8bf07ad9c
Author: Balazs Gibizer <email address hidden>
Date: Wed Nov 24 15:55:35 2021 +0100
Reproduce bug 1917645
The [oslo_messaging _notification] retry parameter is not applied during
connecting to the message bus. But the documentation implies it should[1][2].
The two possible drivers, rabbit and kafka, behaves differently.
1) The rabbit driver will retry the connection forever, blocking the caller
process.
2) The kafka driver also ignores the retry configuration but the
notifier call returns immediately even if the notification is not
(cannot) be delivered.
This patch adds test cases to show the wrong behavior.
[1] https:/ /docs.openstack .org/oslo. messaging/ latest/ configuration/ opts.html# oslo_messaging_ notifications. retry /github. com/openstack/ oslo.messaging/ blob/feb72de7b8 1e3919dedc697f9 fb5484a92f85ad8 /oslo_messaging /notify/ messaging. py#L31- L36
[2] https:/
Related-Bug: #1917645
Change-Id: Id8557050157aec d3abd75c9114d3f caecdfc5dc9 42cbc37a0f5fe1f d7a095dd7f) d9067d97cd801f9 f58c813e41)
(cherry picked from commit 1db6de63a868127
(cherry picked from commit 7390034e479c044