Add doc section on expectations of clean tenants
Every few weeks we get people filing bugs because they're using creds
with pre-existing resources created in an accounts.yaml and list tests
start randomly failing. This adds documentation to say don't do that
because it breaks the isolation expectation of tests.
Change-Id: I6d31a8309d17c72748c4c6283fb6d014f7493463
diff --git a/doc/source/configuration.rst b/doc/source/configuration.rst
index e4b104f..6c55015 100644
--- a/doc/source/configuration.rst
+++ b/doc/source/configuration.rst
@@ -135,7 +135,10 @@
It is worth pointing out that each set of credentials in the accounts.yaml
should have a unique project. This is required to provide proper isolation
to the tests using the credentials, and failure to do this will likely cause
-unexpected failures in some tests.
+unexpected failures in some tests. Also, ensure that these projects and users
+used do not have any pre-existing resources created. Tempest assumes all
+tenants it's using are empty and may sporadically fail if there are unexpected
+resources present.
When the keystone in the target cloud requires domain scoped tokens to
perform admin actions, all pre-provisioned admin users must have a role