tree 77d210e4758cb10de32b03987815a30ffff91e47
parent cfa1fd4b3fa3505b8db2d0abc67b423b2f8b2171
author Dan Smith <danms@us.ibm.com> 1345742981 -0700
committer Dan Smith <danms@us.ibm.com> 1346177827 -0700

Prevent stale isolated tenants from blocking test runs

Especially while developing tests, it's easy to kill a test before
it has a chance to clean up the tenants it has created for isolation.
Since the database has a lot of consistency requirements, it's non-
trivial to go clean these up, and (for me) re-running stack.sh is
the quickest path to a running system again (which is annoying).

This patch adds a configuration option that can allow the tenant
creation to avoid the failure by re-using the existing tenant/user
already present. I think it's safe to have this enabled by default
since it only happens if tenant isolation is enabled.

Also, this augments the error message for the condition (in the case
that the configuration option is disabled) to better indicate
what is happening.

Change-Id: I97052b827ca1b2076ac67025539339b39d3260ae