Use client_retry_limit for keystone connection retry

Use the existing client_retry_limit option.

Change-Id: If3dd260cad088c9783e4c31ba18d7f261f7d68c9
Closes-Bug: #1840235
Task: 36287
This commit is contained in:
Rabi Mishra 2019-08-15 14:54:28 +05:30
parent 70962a434e
commit 54f1119d69
3 changed files with 5 additions and 2 deletions

View File

@ -38,6 +38,8 @@ from heat.engine import clients
LOG = logging.getLogger(__name__)
cfg.CONF.import_opt('client_retry_limit', 'heat.common.config')
# Note, we yield the options via list_opts to enable generation of the
# sample heat.conf, but we don't register these options directly via
# cfg.CONF.register*, it's done via ks_loading.register_auth_conf_options
@ -122,6 +124,7 @@ class RequestContext(context.RequestContext):
self._session = None
self._clients = None
self._keystone_session = session.Session(
connect_retries=cfg.CONF.client_retry_limit,
**config.get_ssl_options('keystone'))
self.trust_id = trust_id
self.trustor_user_id = trustor_user_id

View File

@ -42,7 +42,7 @@ jmespath==0.9.3
jsonpatch==1.21
jsonpointer==2.0
jsonschema==2.6.0
keystoneauth1==3.4.0
keystoneauth1==3.18.0
keystonemiddleware==4.17.0
kombu==4.0.0
linecache2==1.0.0

View File

@ -7,7 +7,7 @@ Babel!=2.4.0,>=2.3.4 # BSD
croniter>=0.3.4 # MIT License
cryptography>=2.1 # BSD/Apache-2.0
eventlet!=0.18.3,!=0.20.1,!=0.21.0,!=0.23.0,!=0.25.0,>=0.18.2 # MIT
keystoneauth1>=3.4.0 # Apache-2.0
keystoneauth1>=3.18.0 # Apache-2.0
keystonemiddleware>=4.17.0 # Apache-2.0
lxml!=3.7.0,>=3.4.1 # BSD
netaddr>=0.7.18 # BSD