quantum-db-manage failed with db migration scripts have branches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Akihiro Motoki |
Bug Description
down_revision of 1b693c095aa3_
2a6d0b51f4bb_
$ quantum-db-manage \
--config-file /etc/quantum/
--config-file /etc/quantum/
stamp head
INFO [alembic.migration] Context impl MySQLImpl.
INFO [alembic.migration] Will assume non-transactional DDL.
Only a single head supported so far...
$ quantum-db-manage \
--config-file /etc/quantum/
--config-file /etc/quantum/
history
1d76643bcec4 -> 1b693c095aa3 (head), Quota ext support added in Grizzly
1d76643bcec4 -> 2a6d0b51f4bb (head), cisco plugin cleanup
3cb5d900c5de -> 1d76643bcec4 (branchpoint), nvp_netbinding
48b6f43f7471 -> 3cb5d900c5de, security_groups
5a875d0e5c -> 48b6f43f7471, DB support for service types
folsom -> 5a875d0e5c, ryu
None -> folsom, folsom initial database
tags: | added: db |
Changed in quantum: | |
milestone: | none → grizzly-3 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-3 → 2013.1 |
When many parallel reviews are going, such cases can easily occur from now on.
My idea is that adding a proper db migration script check to PEP8 test.
Since PEP8 test is executed by Jenkins, we can avoid db migration script branches.