Comment 1 for bug 1744670

I am not sure what is happening here that is causing the certificate information to not be passed down. It seems like cinderclient is using requests directly (in Pike). And whatever else is calling keystoneauth is not passing the cert value to keystoneauth. If the cert values are not passed to keystone auth it is not possible for KSA to understand where to get the cert information from.

I am not sure what we need to do to solve this directly or if it is still an issue. Can you post your tracebackes/errors?

Marking incomplete until we have more information.