Migration error 2.10.2

[aaronchar]

Environment

• Python version: 3.9
• NetBox version: migration from 2.9.9 to 2.10.2

Steps to Reproduce

1. Run Migrations

Expected Behavior

Clean migration to v2.10.2

Observed Behavior

  Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, taggit, tenancy, users, virtualization
Running migrations:
  Applying dcim.0117_custom_field_data... OK
  Applying dcim.0118_inventoryitem_mptt... OK
  Applying dcim.0119_inventoryitem_mptt_rebuild... OK
  Applying dcim.0120_cache_cable_peer...
    Updating console port cable peers...
    Updating console server port cable peers...
    Updating power port cable peers...
    Updating power outlet cable peers...
    Updating interface cable peers...
    Updating front port cable peers...
    Updating rear port cable peers...
    Updating power feed cable peers...
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.ObjectInUse: cannot CREATE INDEX "dcim_interface" because it has pending trigger events


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/netbox/netbox/./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 330, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 371, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 85, in wrapped
    res = handle_func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 243, in handle
    post_migrate_state = executor.migrate(
  File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 229, in apply_migration
    migration_recorded = True
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 115, in __exit__
    self.execute(sql)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 142, in execute
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.9/site-packages/cacheops/transaction.py", line 93, in execute
    result = self._no_monkey.execute(self, sql, params)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.OperationalError: cannot CREATE INDEX "dcim_interface" because it has pending trigger events

[gmurman770]

Experiencing the same behavior.

[aaronchar]

@gmurman770 I still haven't found a resolution for this, I had tested manually running the migrations commands directly in the database and they ran correctly. I haven't had anymore time to look at this since it was moved to a discussion topic.

[gmurman770]

So did you finally succeed in upgrading the whole system? If yes, can you plz provide these migrations commands for me to try them too?

[aaronchar]

Sorry I should have been more clear, it's still not working for me . I was just simply implying that actually database command's that are generated don't seem to generate any errors when executed manually. But there is also some python code that gets run. So I'm still at a loss.

…

On Mon., Jan. 18, 2021, 01:08 gmurman770 ***@***.***> wrote: So did you finally succeed in upgrading the whole system? If yes, can you plz provide these *migrations commands* for me to try them too? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5521 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBIMN5S65WJOPQXJV4LHV3S2PM5FANCNFSM4WEEXZQQ> .

[gmurman770]

@DefunctExodus, hello! Looks like I found a solution at https://docs.djangoproject.com/en/3.1/ref/migration-operations/:
After adding atomic = False into the Migration class script finished successfully.

[artscout]

@DefunctExodus, hello! Looks like I found a solution at https://docs.djangoproject.com/en/3.1/ref/migration-operations/:
After adding atomic = False into the Migration class script finished successfully.

Where exactly did you put that? Cause I've tried toput atomic=False to runpython function in migration script with no avail...

[aaronchar]

got it working

@artscout if you edit the dcim/migrations/0120_cache_cable_peer migration file and add atomic = False into the the migration class section it should work.

worked fine for me

[gmurman770]

@artscout line 50 is the right place ;)

[manuqs33]

Hey I was having the same problem, and it was a pretty stupid mistake in my case, I was applying migrations from the general terminal and I got this error. I tried later from the Django shell and it worked