If a custom CA file is configured via nova_ca_certificates_file,
currently communication with Keystone will fail, since the session is
not created using this CA file. The same is true for nova_api_insecure.
This change fixes the issue by using a keystoneauth session loader.
Closes-Bug: #1873736
Change-Id: I54a4f398a06c61e0f6f8f3efd3e4b6214bca756b
(cherry picked from commit 3bd82c776c91bdd1caee474f3fc9cda18927da7f)
Reviewed: https:/ /review. opendev. org/749203 /git.openstack. org/cgit/ openstack/ masakari/ commit/ ?id=1dd743aed31 7c2550fbd089cf1 3f518c9fec7aba
Committed: https:/
Submitter: Zuul
Branch: stable/ussuri
commit 1dd743aed317c25 50fbd089cf13f51 8c9fec7aba
Author: Mark Goddard <email address hidden>
Date: Fri Jul 17 18:57:21 2020 +0000
Fix CA file for nova client
If a custom CA file is configured via nova_ca_ certificates_ file,
currently communication with Keystone will fail, since the session is
not created using this CA file. The same is true for nova_api_insecure.
This change fixes the issue by using a keystoneauth session loader.
Closes-Bug: #1873736
Change-Id: I54a4f398a06c61 e0f6f8f3efd3e4b 6214bca756b 1caee474f3fc9cd a18927da7f)
(cherry picked from commit 3bd82c776c91bdd