So that the effects of not using the schema SQL file can be seen.
Signed-off-by: Cleber Rosa <[email protected]>
---
installation_support/autotest-database-turnkey | 24 +-----------------------
1 file changed, 1 insertion(+), 23 deletions(-)
diff --git a/installation_support/autotest-database-turnkey
b/installation_support/autotest-database-turnkey
index a7a0a13..209e566 100755
--- a/installation_support/autotest-database-turnkey
+++ b/installation_support/autotest-database-turnkey
@@ -20,8 +20,7 @@ try:
except ImportError:
import common
-from autotest.database.migrate import MigrationManager
-from autotest.database.database_connection import DatabaseConnection
+from autotest.client.shared import global_config
from autotest.frontend import setup_django_environment
try:
@@ -245,27 +244,6 @@ class App(object):
"and setting privileges")
return -1
- # Run the migration manager
- database = DatabaseConnection()
- database.connect('mysql',
- opts.host,
- opts.username,
- opts.password,
- opts.database)
- migrations_dir = os.path.join(os.path.dirname(__file__),
- '..', 'frontend', 'migrations')
- manager = MigrationManager(database,
- migrations_dir=migrations_dir,
- force=True)
- try:
- manager._migrate_from_base()
- manager.do_sync_db(None)
- except AssertionError:
- logging.debug('Error while syncing database schema to '
- 'latest version')
- return -1
-
-
# Finally run Django's syncdb, yes, twice
# The current method is suboptimal, we may need to fetch the
syncdb command module
argv = ['manage.py', 'syncdb', '-v0', '--noinput']
--
1.7.11.7
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
