ensure isolated test cases run with an isolated tenant
If some test cases run with the same tenant and in muiltprocess(using
'testr run --parallel'), race problem will raise. Because one test
case maybe delete the tenant in tearDownClass, but at the sametime
another test case run in another process have passed the setUpClass
stage, the AuthenticationFailure will arises. like this:
"AuthenticationFailure: Authentication with user
FlavorsTestJSON-user and password pass failed"
Part of blueprint speed-up-tempest
Change-Id: Ie840e02778165182461b2b0802db523b354a9b05
diff --git a/tempest/tests/compute/base.py b/tempest/tests/compute/base.py
index a79f7f5..4040705 100644
--- a/tempest/tests/compute/base.py
+++ b/tempest/tests/compute/base.py
@@ -100,7 +100,7 @@
operate in an isolated tenant container.
"""
admin_client = cls._get_identity_admin_client()
- rand_name_root = cls.__name__
+ rand_name_root = rand_name(cls.__name__)
if cls.isolated_creds:
# Main user already created. Create the alt one...
rand_name_root += '-alt'