grenade/projects/60_nova
Surya Seetharaman dc7f4a4ba5 Do the api_db sync before db sync
This patch swaps the order of doing api_db sync with db_sync.
The API database migration should be run before the migrations for
the main/cell databases. This is because the former contains
information about how to find and connect to the latter.

This was discovered in Rocky since we added a data model change
(a new column to the cell_mappings table) that depends on db sync
being run after having added this new column to the api_db (i.e running
api_db sync before db sync). The data model change was the first time
where the actual sync order became meaningful.

This has been correctly done in devstack and the fact that grenade was
doing the db sync before api_db sync was hidden by the fact that
devstack had run at least once before reaching this part of grenade,
which meant that the database was already initialized.

Change-Id: Ic790ef7c3531c2b672621310524797548246b2ef
Closes-Bug: #1761775
2018-04-06 16:05:03 +00:00
..
from-kilo Namespace XTRACE calls 2015-10-28 11:04:25 +11:00
from-liberty Upgrade rootwrap configuration for Nova Compute 2016-01-06 00:48:21 -08:00
from-mitaka Fix cellsv2 cell0 database name 2017-01-15 16:53:53 -05:00
from-newton Run the placement service when upgrading to Ocata 2017-01-27 16:32:38 -08:00
from-ocata Support setting CELLSV2_SETUP variable 2017-07-26 10:35:12 -07:00
within-kilo Nova's flavor migration should be run within-kilo not from-kilo 2015-07-02 12:49:46 -07:00
resources.sh Stop using openstack server remove floating ip 2018-01-27 21:18:16 -05:00
settings Do not fail when saving databases 2017-08-12 17:36:01 -04:00
shutdown.sh Shutdown placement at the end of the base run 2017-12-05 23:50:00 +00:00
upgrade.sh Do the api_db sync before db sync 2018-04-06 16:05:03 +00:00