diff options
| author | Balazs Gibizer <balazs.gibizer@est.tech> | 2021-11-24 15:55:35 +0100 |
|---|---|---|
| committer | Balazs Gibizer <balazs.gibizer@est.tech> | 2021-11-24 16:01:34 +0100 |
| commit | 1db6de63a86812742cbc37a0f5fe1fd7a095dd7f (patch) | |
| tree | 78f229f9dfcc396c2e4a077201f59c2ca95f032f /oslo_messaging/_drivers/common.py | |
| parent | feb72de7b81e3919dedc697f9fb5484a92f85ad8 (diff) | |
| download | oslo-messaging-1db6de63a86812742cbc37a0f5fe1fd7a095dd7f.tar.gz | |
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
[2] https://github.com/openstack/oslo.messaging/blob/feb72de7b81e3919dedc697f9fb5484a92f85ad8/oslo_messaging/notify/messaging.py#L31-L36
Related-Bug: #1917645
Change-Id: Id8557050157aecd3abd75c9114d3fcaecdfc5dc9
Diffstat (limited to 'oslo_messaging/_drivers/common.py')
0 files changed, 0 insertions, 0 deletions