Comment 6 for bug 1963119

Hi,

to be honest, I find the force_tenant_isolation variable confusing too. (e.g.: I would personally prefer the name force_dynamic_credential, but I guess there is a reason why was this name chosen.)

I believe that using dynamic credentials when 'force_tenant_isolation = True' is intended behavior [1][2].

I see two things we can do here:
1) Extend the pre-provisioned credentials section in tempest documentation with information that there are tests that will try to use dynamic_credentials even though the auth.use_dnamic_credentials = False.

2) And to resolve the issue mentioned in this bug we have to find a way how to make tests aware of the resources of the pre-provisioned credentials.

I am not 100 % sure that the solution in this patch is ok [3]. I think it would fix this issue for now but another one might appear in future. I am thinking of the scenario in which there are pre-provisioned credentials and all of them have a network. What would happen if there is a test that does not need a network however it is ok for the test to have credentials with a network? I think the test would fail but I can be wrong.

[1] https://github.com/openstack/tempest/blob/9625f0d364c79f4444c6ac8f7900a3731fbe2d07/tempest/common/credentials_factory.py#L132
[2] https://github.com/openstack/tempest/blob/7e96c8e854386f43604ad098a6ec7606ee676145/tempest/tests/common/test_credentials_factory.py#L153
[3] https://review.opendev.org/c/openstack/tempest/+/831784