Database migration can incorrectly drop owner column on downgrade

[Johannes Erdfelt]

While fixing bug 1204940, I found that migration 009 can incorrectly drop the owner column during downgrade. This appears to only happen with sqlite and is because the get_images_table() doesn't have the correct schema, missing the owner column.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/38644

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/38644
Committed: http://github.com/openstack/glance/commit/773b720b513130468ed615a968103c922d817577
Submitter: Jenkins
Branch: master

commit 773b720b513130468ed615a968103c922d817577
Author: Johannes Erdfelt <email address hidden>
Date: Thu Jul 25 02:18:49 2013 +0000

    Make sure owner column doesn't get dropped during downgrade

    Fixes bug 1204941

    The owner column was missing from the table schema. Because of limitations
    of sqlite and implementation details in SQLAlchemy-migrate, this would end
    up dropping the owner column during a downgrade when using sqlite.

    Change-Id: If8f7f16c9b6fb059f0fcfdf8967afd37f19864b6