DB Migration 14 fails when applied to running system
Bug #1042925 reported by
Brian Waldon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Critical
|
Brian Waldon |
Bug Description
Here's a set of steps to reproduce this issue:
1) Build an Essex deployment of Glance - this will leave the db at version 13
2) Check out the Folsom code
3) Run the Folsom version of glance-manage db_sync - it will attempt to upgrade to 14+
This will result in duplicate table error on 'image_tags'. What's happening is as soon as bin/glance-manage is run, the database models are automatically created. When the migration goes to run, specifically the one that adds the image_tags table, the new table already exists.
This doesn't affect new systems that aren't migrating through version 14
Changed in glance: | |
status: | Fix Committed → In Progress |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/12071
Review: https:/