Merge "Flush tenant membership deletion before user"
2 days prior to this bug being reported, would probably fix the symptoms (but not the underlying cause) - its still racy today. See the referenced bug 998137. A small tweak will make this more obvious I think, as an initial refactoring step before changing the schema.
Checked the sqlalchemy code, the deleted state is a dict, so the carefully ordered code in the sql delete_tenant and delete_user is not guaranteed.
commit 3c9c38a8e08dd03 00a04edb843a0b3 e49486e86f
Merge: 4c8a101 2e912f4
Author: Jenkins <email address hidden>
Date: Tue May 15 07:05:04 2012 +0000
Merge "Flush tenant membership deletion before user"
2 days prior to this bug being reported, would probably fix the symptoms (but not the underlying cause) - its still racy today. See the referenced bug 998137. A small tweak will make this more obvious I think, as an initial refactoring step before changing the schema.