Database downgrades do not work, no tests
Bug #854905 reported by
Brian Lamar
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Hengqing Hu |
Bug Description
When attempting to downgrade the Nova database using migrate's manage.py I get the following error:
http://
1) This error should be fixed
2) Tests should be run to ensure the database can be migrated from 1 -> X and X -> 1 (see Glance' test_migrations for a good example).
Changed in nova: | |
assignee: | nobody → Hengqing Hu (hudayou) |
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fixing migration 031 is easy enough:
+ # grab tables virtual_ interfaces' , meta, autoload=True)
+ fixed_ips = Table('fixed_ips', meta, autoload=True)
+ virtual_interfaces = Table('
See the attached patch too....
However there are many other nova migrations which don't even attempt. Have a look at 030 (multi nic) which just throws an a data loss exception. I'm not sure there is always a good solution when performing the downgrades however I do agree that we should always attempt to do them.