To reproduce:
- using the diablo branch or packages
- configure to use sqlite
- ensure the database doesn't exist
- run glance-registry, observe the database is auto-created
- shut down glance-registry again
- version control the database (see bug #966242)
- switch to the essex branch or packages
- try to upgrade the database using 'glance-manage upgrade'
This is the error:
2012-03-27 14:19:07 13803 INFO [glance.registry.db.migration] Upgrading sqlite:///glance.sqlite to version latest
2012-03-27 14:19:07 13803 INFO [migrate.versioning.api] 9 -> 10...
2012-03-27 14:19:07 13803 INFO [migrate.versioning.api] done
2012-03-27 14:19:07 13803 INFO [migrate.versioning.api] 10 -> 11...
/home/markmc/git/openstack/glance/.venv/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'size'
...
File "/home/markmc/git/openstack/glance/glance/registry/db/migrate_repo/versions/011_make_mindisk_and_minram_notnull.py", line 27, in upgrade
images.c.min_disk.alter(nullable=False)
...
File "/home/markmc/git/openstack/glance/.venv/lib/python2.7/site-packages/sqlalchemy/sql/compiler.py", line 1875, in visit_null
raise NotImplementedError("Can't generate DDL for the null type")
NotImplementedError: Can't generate DDL for the null type
The problem stems from the fact that the auto-creation of the database with register_models() - as opposed to its creation using db_sync - creates a BIGINT column. When we try and upgrade, sqlalchemy doesn't recognize the type and sets it to NullType which the DDL compiler can't handle.
One solution would be to make sure the register_models() codepath doesn't create a BigInteger column with sqlite.
Another solution would be to just auto-create the DB using db_sync().
OK, finally twigged that in order to reproduce this issue, the starting point version must be 9 as opposed to zero.
Whereas the instructions as stated will cause the version field in the migrate_version table to be set to zero, as the the following commit to allow a specific version be specified has not yet been applied to the stable diablo branch (and isn't directly applicable):
https:/
Otherwise the Essex upgrade from version 0 fails with:
http://
I've backported the "Allow specifying the current version in 'glance-manage version_control'" commit to diablo stable:
https:/
and with that patch in place, the bug is reproducible if the target version is explicitly set to 9:
sudo ./tools/
before switching to the Essex branch.