> Workaround is using keystoneclient.v2_0.client.
Looks like it's the only fix we can provide right now. Moreover, the similar way behaves our UI - just performs request on keystone, and don't rediscover its endpoint.
> Workaround is using keystoneclient. v2_0.client.
Looks like it's the only fix we can provide right now. Moreover, the similar way behaves our UI - just performs request on keystone, and don't rediscover its endpoint.