This reverts commit 810417df865c7b4eb71cee4dfee843d65972852b.
The Swift driver not being able to use Trusts had nothing to do
about the store driver itself nor that keystoneauth1 would have
broken the feature, but rather it not having the functionality
in the first place and us not catching that on reviews.
We should figure out how to test this before we try to replace
this code again.
merge-conflict on requirements jsonschema.
Change-Id: If12a013404296486dc387b099477d1608b24ba63
Closes-Bug: #1916052
(cherry picked from commit 9b683678b2a19bb1069aace58e054150a78b5f6f)
Reviewed: https:/ /review. opendev. org/c/openstack /glance/ +/800103 /opendev. org/openstack/ glance/ commit/ f213c1bf44388fd e5802bd707cf285 0f88a26d5e
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/ussuri
commit f213c1bf44388fd e5802bd707cf285 0f88a26d5e
Author: Erno Kuvaja <email address hidden>
Date: Thu Jun 10 13:51:49 2021 +0100
Revert "Remove all usage of keystoneclient"
This reverts commit 810417df865c7b4 eb71cee4dfee843 d65972852b.
The Swift driver not being able to use Trusts had nothing to do
about the store driver itself nor that keystoneauth1 would have
broken the feature, but rather it not having the functionality
in the first place and us not catching that on reviews.
We should figure out how to test this before we try to replace
this code again.
merge-conflict on requirements jsonschema.
Change-Id: If12a0134042964 86dc387b099477d 1608b24ba63 1069aace58e0541 50a78b5f6f)
Closes-Bug: #1916052
(cherry picked from commit 9b683678b2a19bb