nova_compute fails to start in tls-everywhere configuration
With tls-everywhere enabled connecting to keystone endpoint fails to retrieve the URL for the placement endpoint as the certificate can not be verified. While verification is disabled to check the placement endpoint later, it is not to communicate with keystone. This disables certificate verification for communication with keystone. Related-Bug: 1784155 Change-Id: I317dd62f3a555f375d540a63c21a6fb38d37ca96 (cherry picked from commita99820a80c
) (cherry picked from commit14af0677c8
)
This commit is contained in:
parent
f88dfe5a2d
commit
605d58b116
|
@ -55,7 +55,7 @@ if __name__ == '__main__':
|
|||
project_name=config.get('placement', 'project_name'),
|
||||
project_domain_name=config.get('placement', 'user_domain_name'),
|
||||
auth_url=config.get('placement', 'auth_url')+'/v3')
|
||||
sess = session.Session(auth=auth)
|
||||
sess = session.Session(auth=auth, verify=False)
|
||||
keystone = client.Client(session=sess)
|
||||
|
||||
iterations_endpoint = iterations
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
With tls-everywhere enabled connecting to keystone endpoint fails
|
||||
to retrieve the URL for the placement endpoint as the certificate
|
||||
can not be verified. While verification is disabled to check the
|
||||
placement endpoint later, it is not to communicate with keystone.
|
||||
This disables certificate verification for communication with
|
||||
keystone.
|
Loading…
Reference in New Issue