cinder: Double [DEFAULT]/rpc_response_timeout to 120
Bug #1873234 documents a number of CI failures caused by RPC requests from c-api to c-vol timing out due to `lvchange` taking longer than the default rpc_response_timeout of 60 seconds to complete. While the underlying reason for the slowness should be investigated by the cinder team a trivial workaround to the fallout created by these timeouts is to simply double the client RPC timeout used by c-api, allowing c-vol to return and overall the request to succeed. Change-Id: I53dc0ae10af6aa13f1349b58373932eb6a15ab02 Related-Bug: #1873234
This commit is contained in:
parent
a9afdb18b4
commit
fc41717222
@ -236,6 +236,11 @@ function configure_cinder {
|
||||
iniset $CINDER_CONF key_manager backend cinder.keymgr.conf_key_mgr.ConfKeyManager
|
||||
iniset $CINDER_CONF key_manager fixed_key $(openssl rand -hex 16)
|
||||
|
||||
# Avoid RPC timeouts in slow CI and test environments by doubling the
|
||||
# default response timeout set by RPC clients. See bug #1873234 for more
|
||||
# details and example failures.
|
||||
iniset $CINDER_CONF DEFAULT rpc_response_timeout 120
|
||||
|
||||
if is_service_enabled c-vol && [[ -n "$CINDER_ENABLED_BACKENDS" ]]; then
|
||||
local enabled_backends=""
|
||||
local default_name=""
|
||||
|
Loading…
Reference in New Issue
Block a user