Issue during upgrade from 3.2.6 to 3.3.6

[muzaffarhal]

NetBox version
v3.2.6

Python version
3.8

OS
Ubuntu 20.04

Steps to Reproduce
Upgrade the NetBox from 3.2.6 to 3.3.6
Error on running migrations on populate_cable_terminations

Observed Behavior
Running migrations:
Applying dcim.0154_half_height_rack_units... OK
Applying dcim.0155_interface_poe_mode_type... OK
Applying dcim.0156_location_status... OK
Applying dcim.0157_new_cabling_models... OK
Applying dcim.0158_populate_cable_terminations...
Updated 6200/7074 cables (87.64%)Traceback (most recent call last):
File "netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/base.py", line 414, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/base.py", line 460, in execute
output = self.handle(*args, **options)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/base.py", line 98, in wrapped
res = handle_func(*args, **kwargs)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 290, in handle
post_migrate_state = executor.migrate(
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 131, in migrate
state = self._migrate_all_forwards(
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 163, in migrate_all_forwards
state = self.apply_migration(
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 248, in apply_migration
state = migration.apply(state, schema_editor)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/migrations/migration.py", line 131, in apply
operation.database_forwards(
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/migrations/operations/special.py", line 193, in database_forwards
self.code(from_state.apps, schema_editor)
File "/opt/netbox-3.3.6/netbox/dcim/migrations/0158_populate_cable_terminations.py", line 54, in populate_cable_terminations
termination = termination_model.objects.get(pk=cable[f'termination{cable_end}_id'])
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/opt/netbox-3.3.6/venv/lib/python3.8/site-packages/django/db/models/query.py", line 496, in get
raise self.model.DoesNotExist(
fake.DoesNotExist: ConsolePort matching query does not exist.

[candlerb]

Code ref: https://github.com/netbox-community/netbox/blob/v3.4.5/netbox/dcim/migrations/0158_populate_cable_terminations.py#L41-L54

Looks like you have a cable whose endpoint points to a console port that doesn't exist. Unfortunately, these Generic Foreign Keys cannot have their refential integrity enforced by the database itself like regular foreign keys, and so it relies on the Django code to maintain them - which doesn't always do it properly.

What that code is doing is effectively:

select id, termination_a_type, termination_a_id, termination_b_type, termination_b_id from dcim_cable;

and then iterating through those rows to create new cable termination objects. But there's at least one row where either the "a" type/id or "b" type/id points to a non-existent endpoint. Unfortunately, the error doesn't tell you specifically which row this happened on.

You might be able to temporarily modify that file, insert a print(cable.id) in the loop, and find out which cable it's barfing on.

You may be able to filter, in the GUI, down to just those cables which have console ports at either end.

Or it might be possible to write a hairy SQL join along the lines of these - they were for a different case (assigned_object_type and assigned_object_id) but has some similarities to what you're looking for. You'd have to build the query yourself; I don't have a Netbox 3.2 lying around to test with.

You can at least find the content type id for console ports: in my case I get 31 (it may be different for you)

netbox3=# select id from django_content_type where model='consoleport';
 id
----
 31
(1 row)

Then identify all cables which connect to console ports:

select id, termination_a_type, termination_a_id, termination_b_type, termination_b_id from dcim_cable
where termination_a_type=31 or termination_b_type=31;