+++ This bug was initially created as a clone of Bug #1037675 +++ Description of problem: For db migrations in quantum is mandatory to have current stamp stored in alembic_version table. There is a tool quantum-db-manage which is capable of migrations and after each migration it stamps current version. 'quantum-db-manage upgrade head' is probably a good way to create database for quantum with correct stamp. Version-Release number of selected component (if applicable): openstack-packstack-2013.1.1-0.37.dev705.el6ost.noarch.rpm How reproducible: Always Steps to Reproduce: 1. Install quantum using packstack 2. quantum-db-manage --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugin.ini current 3. Actual results: None Expected results: grizzly Additional info: This blocks migration between neutron versions.
Although could be useful if we'll have the data base stamped in the upgrade process then we can skip adding this code to z-stream at this point. If we'll find another reason to stamp the data base we'll reopen this bug.
Note that the neutron packages take care of this via %pretrans and %posttrans scriptlets when upgrading from grizzly.