1212892 - Changes to classifiedfailure and failurematch models not reflected in migrations file

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P1)

Description

[Ed Morley [:emorley]]

From a stage deploy:

    /treeherder.allizom.org/treeherder-env.sh && python2.7 manage.py migrate --noinput (1.519s)
    [localhost] out: Operations to perform:
    [localhost] out: Synchronize unmigrated apps: log_parser, django_browserid, corsheaders, autoclassify, staticfiles, workers, messages, hawkrest, rest_framework_swagger, webapp, rest_framework, embed, rest_framework_extensions, etl
    [localhost] out: Apply all migrations: perf, sessions, admin, sites, auth, contenttypes, credentials, model
    [localhost] out: Synchronizing apps without migrations:
    [localhost] out: Creating tables...
    [localhost] out: Running deferred SQL...
    [localhost] out: Installing custom SQL...
    [localhost] out: Running migrations:
    [localhost] out: No migrations to apply.
    [localhost] out: Your models have changes that are not yet reflected in a migration, and so won't be applied.
    [localhost] out: Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. 

Locally:

vagrant ~/treeherder $ ./manage.py makemigrations
Migrations for 'model':
  0002_auto_20151008_0812.py:
    - Alter field failure_lines on classifiedfailure
    - Alter field failure_line on failurematch

I'm not sure whether it's best to update the initial migration file, or create a new one.

Comment 1

[Ed Morley [:emorley]]

Mauro/James, could one of you take a look at this?

Comment 2

[Mauro Doglio [:mdoglio]]

I'll have a look this week.

Comment 3

[Ed Morley [:emorley]]

This was fixed in https://github.com/mozilla/treeherder/pull/1067