Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migration failure

See original GitHub issue

Migrating from python-social-auth to social-core / social-django,

$ docker-compose exec web python manage.py migrate
Traceback (most recent call last):
  File "manage.py", line 9, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", line 63, in handle
    executor = MigrationExecutor(connection, self.migration_progress_callback)
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 17, in __init__
    self.loader = MigrationLoader(self.connection)
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/loader.py", line 48, in __init__
    self.build_graph()
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/loader.py", line 233, in build_graph
    self.graph.add_dependency(migration, key, parent)
  File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/graph.py", line 42, in add_dependency
    raise KeyError("Migration %s dependencies reference nonexistent parent node %r" % (migration, parent))
KeyError: u"Migration social_django.0002_add_related_name dependencies reference nonexistent parent node (u'social_django', u'0001_initial')"

Issue Analytics

State:
Created 7 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

4reactions

lukasz-karolewskicommented, Jan 23, 2017

i’m getting

python manage.py migrate
CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0006_partial, 0004_auto_20160423_0400 in social_django).
To fix them run 'python manage.py makemigrations --merge'
(test) ubuntu@ubuntu-xenial:~/test$ python manage.py makemigrations --merge
No conflicts detected to merge.
(test) ubuntu@ubuntu-xenial:~/test$ python manage.py makemigrations social_django --merge
No conflicts detected to merge.

…

0reactions

nijelcommented, Feb 1, 2017

I’ve created https://github.com/python-social-auth/social-app-django/issues/28 for this.

Top Results From Across the Web

7 Reasons Data Migrations Fail | Premier International

Poor Communication: Data Migration is generally part of a larger project and must coordinate reams of changes to complex technical requirements while also ......

System Migration Risks: Why System Migrations Fail | Celonis

System Migration Risks: 7 Reasons Why Migrations Fail · 1. Poorly understood or undocumented legacy processes · 2. Lack of pre-standardization · 3....

Why Do Migrations Fail and What Can We Do about It?

This paper investigates the main causes that make the application migration to Cloud complicated and error-prone through two case studies.

Cloud migration risks: 5 reasons why cloud migrations fail

One of the most common causes behind cloud migration failure is a lack of planning. In fact, this was the most common reason...

Common causes of a migration failure and solutions - Data ...

This topic describes the common causes of a migration failure and solutions when you use Data Transport to migrate data. If a migration...