Dennis, FWIW, I believe there are a couple of problems here but neither of them is related to your advice to manually modify a migration. Problem #1. `django-admin makemigrations` was run, so this 0009_auto_... migration got created. I think the installer doesn't run this command, or does it? Problem #2. The migration 0008 was not in sync with the model, so makemigraitons will create a new migraiton if run. Fixed in 3.3.1. https://pulp.plan.io/issues/6665
Tanya On Fri, May 8, 2020 at 11:15 PM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > No idea where it came from. The timestamp is from 4/25. I run pip > uninstall pulp-rpm and it didn't remove it. > > # ls -ld > /opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py > -rw-rw-r-- 1 pulp mse-python 492 Apr 25 15:32 > /opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py > > # more > /opt/utils/venv/pulp/3.7.3/lib/python3.7/site-packages/pulp_rpm/app/migrations/0009_auto_20200425_1932.py > # Generated by Django 2.2.12 on 2020-04-25 19:32 > > from django.db import migrations, models > > > class Migration(migrations.Migration): > > dependencies = [ > ('rpm', '0008_advisory_pkg_sumtype_as_int'), > ] > > operations = [ > migrations.AlterField( > model_name='updatecollectionpackage', > name='sum_type', > field=models.PositiveIntegerField(choices=[(0, 0), (1, 1), (2, 2), (3, 3), > (4, 4), (5, 5), (6, 6), (7, 7)], null=True), > ), > > > From: [email protected] At: 05/08/20 16:21:45 > To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> > Cc: [email protected] > Subject: Re: [Pulp-list] 3.3.1 migration error > > Hey there! > > On Fri, May 8, 2020 at 3:53 PM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> Hi All, >> Getting an error to upgrade from 3.3. run 'python manage.py >> makemigrations --merge' gave more errors. Anyidea how this can be fixed? >> >> TASK [pulp-database : Run database auth migrations] >> ********************************************************************************************************** >> fatal: [pulp3-2]: FAILED! => {"changed": true, "cmd": >> ["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "auth", >> "--no-input"], "delta": "0:00:03.534845", "end": "2020-05-08 >> 15:44:20.362670", "msg": "non-zero return code", "rc": 1, "start": >> "2020-05-08 15:44:16.827825", "stderr": "CommandError: Conflicting >> migrations detected; multiple leaf nodes in the migration graph: >> (0009_revision_null, 0009_auto_20200425_1932 in rpm).\nTo fix them run >> 'python manage.py makemigrations --merge'", "stderr_lines": ["CommandError: >> Conflicting migrations detected; multiple leaf nodes in the migration >> graph: (0009_revision_null, 0009_auto_20200425_1932 in rpm).", "To fix them >> run 'python manage.py makemigrations --merge'"], "stdout": "", >> "stdout_lines": []} >> > > Where did migration "0009_auto_20200425_1932" come from? Looks like it's > conflicting with the delivered 0009_revision_null and causing your problem. > > G > -- > Grant Gainey > Principal Software Engineer, Red Hat System Management Engineering > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
