Fix no-validation init use case
For the case of no validation, endpoint state should be assumed to be UP. This is a quick fix to unblock no-validation scenarios. Next patch will deal with cluster DOWN->UP transition. Change-Id: Ia2a47e1a8d8aeb0174377b24b469613d866fc805
This commit is contained in:
parent
0ffe769415
commit
3229ffc138
|
@ -589,7 +589,10 @@ class ClusteredAPI(object):
|
||||||
result = self._http_provider.validate_connection(self,
|
result = self._http_provider.validate_connection(self,
|
||||||
endpoint,
|
endpoint,
|
||||||
conn)
|
conn)
|
||||||
if result:
|
if result or endpoint.state == EndpointState.INITIALIZED:
|
||||||
|
# If no endpoint validation is configured, we assume
|
||||||
|
# endpoint is UP on startup, but we shouldn't move it
|
||||||
|
# to UP from DOWN state
|
||||||
endpoint.set_state(EndpointState.UP)
|
endpoint.set_state(EndpointState.UP)
|
||||||
except exceptions.ClientCertificateNotTrusted:
|
except exceptions.ClientCertificateNotTrusted:
|
||||||
LOG.warning("Failed to validate API cluster endpoint "
|
LOG.warning("Failed to validate API cluster endpoint "
|
||||||
|
|
Loading…
Reference in New Issue