As a side note and possible work around: On startup, it seems glance-registry automatically migrates the database. Instead of running 'glance-manage db_sync' against a natty-generated database (which always fails), simply restarting glance-registry appears to bring the db schema up to date. This doesn't solve the issue, but relying on service restart instead of glance-manage may solve the upgrade problem in the meantime.
I believe this issue is being discussed upstream @ https:/ /bugs.launchpad .net/glance/ +bug/824794
As a side note and possible work around: On startup, it seems glance-registry automatically migrates the database. Instead of running 'glance-manage db_sync' against a natty-generated database (which always fails), simply restarting glance-registry appears to bring the db schema up to date. This doesn't solve the issue, but relying on service restart instead of glance-manage may solve the upgrade problem in the meantime.