Migrations have FATAL ERROR

When running the "sentry --config=./sentry.conf.py upgrade' method (from a clean virtualenv, everything just installed) on a Postgresql database, South gives me the following:

Running migrations for sentry:

• Migrating forwards to 0054_fix_project_keys.

  sentry:0001_initial
  sentry:0002_auto__del_field_groupedmessage_url__chg_field_groupedmessage_view__chg
  sentry:0003_auto__add_field_message_group__del_field_groupedmessage_server_name
  sentry:0004_auto__add_filtervalue__add_unique_filtervalue_key_value
  sentry:0005_auto
  sentry:0006_auto
  sentry:0007_auto__add_field_message_site
  sentry:0008_auto__chg_field_message_view__add_field_groupedmessage_data__chg_field
  sentry:0009_auto__add_field_message_message_id
  sentry:0010_auto__add_messageindex__add_unique_messageindex_column_value_object_id
  sentry:0011_auto__add_field_groupedmessage_score
  sentry:0012_auto
  sentry:0013_auto__add_messagecountbyminute__add_unique_messagecountbyminute_group_
  sentry:0014_auto
  sentry:0014_auto__add_project__add_projectmember__add_unique_projectmember_project
  sentry:0015_auto__add_field_message_project__add_field_messagecountbyminute_projec
  sentry:0016_auto__add_field_projectmember_is_superuser
  sentry:0017_auto__add_field_projectmember_api_key
  sentry:0018_auto__chg_field_project_owner
  sentry:0019_auto__del_field_projectmember_api_key__add_field_projectmember_public_
  sentry:0020_auto__add_projectdomain__add_unique_projectdomain_project_domain
  sentry:0021_auto__del_message__del_groupedmessage__del_unique_groupedmessage_proje
  sentry:0022_auto__del_field_group_class_name__del_field_group_traceback__del_field
  sentry:0023_auto__add_field_event_time_spent
  sentry:0024_auto__add_field_group_time_spent_total__add_field_group_time_spent_cou
  sentry:0025_auto__add_field_messagecountbyminute_time_spent_total__add_field_messa
  sentry:0026_auto__add_field_project_status
  sentry:0027_auto__chg_field_event_server_name
  sentry:0028_auto__add_projectoptions__add_unique_projectoptions_project_key_value
  sentry:0029_auto__del_field_projectmember_is_superuser__del_field_projectmember_pe
  sentry:0030_auto__add_view__chg_field_event_group
  sentry:0031_auto__add_field_view_verbose_name__add_field_view_verbose_name_plural_
  sentry:0032_auto__add_eventmeta
  sentry:0033_auto__add_option__add_unique_option_key_value
  sentry:0034_auto__add_groupbookmark__add_unique_groupbookmark_project_user_group
  sentry:0034_auto__add_unique_option_key__del_unique_option_value_key__del_unique_g
  FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_option" ADD CONSTRAINT "sentry_option_45544485" UNIQUE ("key")
  The error was: relation "sentry_option_45544485" already exists

FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_groupmeta" ADD CONSTRAINT "sentry_groupmeta_group_id_5cacc8a6a708a7d5_uniq" UNIQUE ("group_id", "key")
The error was: current transaction is aborted, commands ignored until end of transaction block

FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_projectoptions" ADD CONSTRAINT "sentry_projectoptions_project_id_2d0b5c5d84cdbe8f_uniq" UNIQUE ("project_id", "key")
The error was: current transaction is aborted, commands ignored until end of transaction block

sentry:0036_auto__chg_field_option_value__chg_field_projectoption_value
sentry:0037_auto__add_unique_option_key__del_unique_option_value_key__del_unique_g
FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_option" ADD CONSTRAINT "sentry_option_45544485" UNIQUE ("key")
The error was: relation "sentry_option_45544485" already exists

FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_groupmeta" ADD CONSTRAINT "sentry_groupmeta_group_id_5cacc8a6a708a7d5_uniq" UNIQUE ("group_id", "key")
The error was: current transaction is aborted, commands ignored until end of transaction block

FATAL ERROR - The following SQL query failed: ALTER TABLE "sentry_projectoptions" ADD CONSTRAINT "sentry_projectoptions_project_id_2d0b5c5d84cdbe8f_uniq" UNIQUE ("project_id", "key")
The error was: current transaction is aborted, commands ignored until end of transaction block

sentry:0038_auto__add_searchtoken__add_unique_searchtoken_document_field_token__ad
sentry:0039_auto__add_field_searchdocument_status
sentry:0040_auto__del_unique_event_event_id__add_unique_event_project_event_id
sentry:0041_auto__add_field_messagefiltervalue_last_seen__add_field_messagefilterv
sentry:0042_auto__add_projectcountbyminute__add_unique_projectcountbyminute_projec
sentry:0043_auto__chg_field_option_value__chg_field_projectoption_value
sentry:0044_auto__add_field_projectmember_is_active
sentry:0045_auto__add_pendingprojectmember__add_unique_pendingprojectmember_projec
sentry:0046_auto__add_teammember__add_unique_teammember_team_user__add_team__add_p
sentry:0047_migrate_project_slugs

• Migration 'sentry:0047_migrate_project_slugs' is marked for no-dry-run.
  sentry:0048_migrate_project_keys
• Migration 'sentry:0048_migrate_project_keys' is marked for no-dry-run.
  sentry:0049_create_default_project_keys
• Migration 'sentry:0049_create_default_project_keys' is marked for no-dry-run.
  sentry:0050_remove_project_keys_from_members
  sentry:0051_auto__del_pendingprojectmember__del_unique_pendingprojectmember_projec
  sentry:0052_migrate_project_members
• Migration 'sentry:0052_migrate_project_members' is marked for no-dry-run.
  sentry:0053_auto__del_projectmember__del_unique_projectmember_project_user
  sentry:0054_fix_project_keys
• Migration 'sentry:0054_fix_project_keys' is marked for no-dry-run.
  Created default Sentry project owned by wezzy
  Backfilling project ids for <class 'sentry.models.Group'>.. done!
  Backfilling project ids for <class 'sentry.models.Event'>.. done!
  Backfilling project ids for <class 'sentry.models.FilterValue'>.. done!
  Backfilling project ids for <class 'sentry.models.MessageFilterValue'>.. done!
  Backfilling project ids for <class 'sentry.models.MessageCountByMinute'>.. done!
• Loading initial data for sentry.
  No fixtures found.

[dcramer]

Looks like we're not correctly handling rollbacks in these situations.

Migrations are definitely on the radar to fix (somehow). I think it's likely going to be changing it to some kind of migrate --from-super-old-version and having migrate start fresh from like 4.0 or something for other people.

I want to add that Sentry does work afterwards. But not having certain constraints might end up in unexpected results.

Maybe it's an idea to allow for separate steps on upgrade? If I was to be able to do whatever setup you do after the actual migrations in a separate step I could go in and set the database up from scratch by using the output of SQLALL and then running the code which sets things up. People could then skip migrations and just have the tables created based on the Django models.

South, we love it, we hate it :)

[dcramer]

These should be corrected now