700892 - [mozillians-dev|stage|prod] Run south migrations on update

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Hi we're starting to use Django-South to manage migrations instead of schematic.

So we can take out 

schematic migrations

from our updates and add:

./manage.py syncdb
./manage.py migrate

This needs to happen on dev/stage and prod.

Comment 1

[Jeremy Orem [:oremj]]

Is it okay to run that in prod at any time?

Comment 2

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

oremj - it should do nothing significant at the moment, but when we do push, it will be okay to run at any time, south will NOOP unless there's migrations.

Comment 3

[tofumatt [:tofumatt]]

For what it's worth, I ran this on the dev server and got the following:

Running migrations for users:
 - Migrating forwards to 0002_auto__add_field_userprofile_is_vouched__add_field_userprofile_vouched_.
 > users:0001_initial
 ! Error found during real run of migration! Aborting.

 ! Since you have a database that does not support running
 ! schema-altering statements in transactions, we have had 
 ! to leave it in an interim state between migrations.

! You *might* be able to recover with:   = DROP TABLE `profile` CASCADE; []
   = DROP TABLE `profile_groups` CASCADE; []

 ! The South developers regret this has happened, and would
 ! like to gently persuade you to consider a slightly
 ! easier-to-deal-with DBMS.
 ! NOTE: The error which caused the migration to fail is further up.

That is not good.

Comment 4

[tofumatt [:tofumatt]]

To avoid the error:

INSERT INTO `south_migrationhistory` (`id`, `app_name`, `migration`, `applied`)
VALUES
	(1, 'users', '0001_initial', '2011-11-09 02:41:21');

Comment 5

[Jeremy Orem [:oremj]]

This has been run on dev/stage. The prod part should just be added to the push instructions.

Comment 6

[tofumatt [:tofumatt]]

Just making sure: this has been added to the deploy script, right? These commands replace our old schematic commands, so they'll need to be run on every deploy.

Comment 7

[Jason Thomas [:jason]]

Updated scripts to reflect changes.