You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original issue is in the upstream: when a custom certificate is used and OS_CACERT is set, the discover-tempest-conf still cannot verify the certificate because internally it uses certifi as a CA provider. See https://storyboard.openstack.org/#!/story/2011168.
Once the upstream is fixed, snap-tempest still need to make sure the OS_CACERT path is pointed to a location where the snap is accessible to.
The text was updated successfully, but these errors were encountered:
The original issue is in the upstream: when a custom certificate is used and
OS_CACERT
is set, thediscover-tempest-conf
still cannot verify the certificate because internally it usescertifi
as a CA provider. See https://storyboard.openstack.org/#!/story/2011168.Once the upstream is fixed, snap-tempest still need to make sure the
OS_CACERT
path is pointed to a location where the snap is accessible to.The text was updated successfully, but these errors were encountered: