Tables are generated outside of migration process

[Rick Harris]

Currently SQLALchemy is 'nice' enough to create tables for us if they are not present. In theory this would be great, except that it messes up our migrations.

The reason is, when SQLAlchemy autogenerates the tables, it doesn't include a schema_version...so, when someone subsequently run db_sync it attempts to create the tables that are already there.

The solution here is probably to disable the autocreation of tables.

[Jay Pipes (jaypipes)]

I think the solution here is not to disable the autocreation of tables but instead to put a try: except block around the code in db_sync in nova-manage that catches the predictable table already exists error, and simply sets the the schema_version record to the last DB version in the migrate_repo... I'll have a stab at this.

[Jay Pipes (jaypipes)]

I'd love to see migrations standardized and cleaned up across most core projects, actually ... I'm not getting anywhere with this branch and am going to push it off until Folsom I think...

[Bernhard M. Wiedemann (ubuntubmw)]

I tried to reproduce this issue, but it just worked here for sqlite, mysql and postgresql.
While starting glance before db_sync did create tables without version, a subsequent db_sync returned without error and did add the version to the DB.

[Mark McLoughlin (markmc)]

rc3 glance automatically version controls auto-created DBs. See bug #966241

[Jay Pipes (jaypipes)]

OK, I'm going to mark this bug Fix Released, then...