Tests Fail
Bug #843082 reported by
klmitch
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Unassigned |
Bug Description
The run_tests.py file assumes databases are in the same file as the test directory. But Keystone creates the databases in the current directory.
So running <pre>python keystone/
To post a comment you must log in.
This is now succeeding, however the underlying problem remains: run_tests.py attempts to delete existing databases in the keystone/test directory, while the default keystone.conf writes databases to the current working directory.
This means that after tests have been run once from the top src directory, databases will be written to the top src directory, and never deleted by the test script.
The caveat to changing run_tests.py to delete databases from the cwd is that if run_tests.py is executed in production for whatever reason, production data could be lost (assuming a default keystone.conf).
I believe the best solution is to have (one or more) keystone.conf designed for exclusive use by run_tests.py (see issue #115: https:/ /github. com/rackspace/ keystone/ issues/ 115 ), which put databases in a different location, say, /tmp/. Or even better, keep it in memory (see issue #112: https:/ /github. com/rackspace/ keystone/ issues/ 112 ).