The rabbit driver was using the rpc_response_timeout configuration
option as a reconnect timeout value, even though the option was defined
only in oslo_messaging.client and was not always being registered before
being accessed. An earlier patch fixed this by registering the option
here in the driver, too, but that breaks several levels of
abstraction. This changes the driver to define a new option with the
same default value, so that the driver is only using options it defines
itself. It also removes the old hacky fix.
Reviewed: https:/ /review. openstack. org/188163 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=a0b33a46598 499c47ac90eba26 f27bff4eab991c
Committed: https:/
Submitter: Jenkins
Branch: master
commit a0b33a46598499c 47ac90eba26f27b ff4eab991c
Author: Doug Hellmann <email address hidden>
Date: Wed Jun 3 19:53:27 2015 +0000
replace rpc_response_ timeout use in rabbit driver
The rabbit driver was using the rpc_response_ timeout configuration client and was not always being registered before
option as a reconnect timeout value, even though the option was defined
only in oslo_messaging.
being accessed. An earlier patch fixed this by registering the option
here in the driver, too, but that breaks several levels of
abstraction. This changes the driver to define a new option with the
same default value, so that the driver is only using options it defines
itself. It also removes the old hacky fix.
Closes-bug: #1461182
Change-Id: Ia96c815d157219 e12a10d94b87b01 56503369a6b