Sometimes we have case where we want to upgrade the 3rd party packages. But, we have case where the migration files were totally different with the old version.

For example in my case, while upgrading the dj-stripe version, the migration files were totally different. And it causing inconsistent migration history or other migration issues.

So, to fix this we need to reset the django_migrations table after deployment is done, then restart the pods/containers.

Change the migration files

You need to change all migration files that has relation with 3rd party packages, and change the dependencies to the newest version of 3rd party packages. For example, inside file of myproject/users/migrations/0005_auto_20210117_0220.py have dependency to the related 3rd party package.

So, you need to change the dependencies of package to the newest version from 3rd party packages.

class Migration(migrations.Migration):

    dependencies = [
        ('djstripe', '0006_2_3'),
        ('users', '0004_auto_20201231_1454'),
    ]

For example in above case, I change the '0006_2_3' to '0011_2_7' where it’s the latest version from 3rd party package that I want to upgrade. https://github.com/dj-stripe/dj-stripe/blob/2.7.1/djstripe/migrations/0011_2_7.py

a. Steps for Docker:

1. Deploy
2. Execute below commands:

docker exec -it <postgres_container_name_or_id> psql -U <username> <database_name>
DROP TABLE django_migrations;

Then:

docker-compose -f local.yml run django python manage.py migrate --fake
docker-compose -f local.yml run django python manage.py migrate

1. Then restart all containers.

b. Steps for k8s pod:

1. Deploy
2. Execute below commands:

Run this in the postgres database:

psql -U <username> <database_name>
DROP TABLE django_migrations;

Then, migrate the table;

kubectl --kubeconfig=/path/to/kubeconfig get pods | grep django
kubectl --kubeconfig=/path/to/kubeconfig exec --stdin --tty django-xxxxx -- /bin/bash

source /entrypoint

python manage.py migrate --fake
python manage.py migrate

1. Then restart all pods.