Upgrade failed with DB migration

[echobops]

I recently upgraded to Netbox version 3.1.7 and the database migration failed somehow. I'm getting this error when trying to load the site now:

The corresponding Postgres error:

I attempted to run migration manually as it suggests, but with no success:

root@c2263bc79785:/app/netbox/netbox# python3 manage.py migrate
/app/netbox/netbox/netbox/settings.py:57: UserWarning: The CACHE_TIMEOUT configuration parameter was removed in v3.0.0 and no longer has any effect.
  warnings.warn(
/app/netbox/netbox/netbox/settings.py:61: UserWarning: The RELEASE_CHECK_TIMEOUT configuration parameter was removed in v3.0.0 and no longer has any effect.
  warnings.warn(
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/django/db/migrations/loader.py", line 259, in build_graph
    self.graph.validate_consistency()
  File "/usr/lib/python3.9/site-packages/django/db/migrations/graph.py", line 195, in validate_consistency
    [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
  File "/usr/lib/python3.9/site-packages/django/db/migrations/graph.py", line 195, in <listcomp>
    [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
  File "/usr/lib/python3.9/site-packages/django/db/migrations/graph.py", line 58, in raise_error
    raise NodeNotFoundError(self.error_message, self.key, origin=self.origin)
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0131_consoleport_speed dependencies reference nonexistent parent node ('dcim', '0130_sitegroup')

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

Traceback (most recent call last):
  File "/app/netbox/netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.9/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3.9/site-packages/django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.9/site-packages/django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python3.9/site-packages/django/core/management/base.py", line 89, in wrapped
    res = handle_func(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 92, in handle
    executor = MigrationExecutor(connection, self.migration_progress_callback)
  File "/usr/lib/python3.9/site-packages/django/db/migrations/executor.py", line 18, in __init__
    self.loader = MigrationLoader(self.connection)
  File "/usr/lib/python3.9/site-packages/django/db/migrations/loader.py", line 53, in __init__
    self.build_graph()
  File "/usr/lib/python3.9/site-packages/django/db/migrations/loader.py", line 276, in build_graph
    raise NodeNotFoundError(
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0131_consoleport_speed depends on nonexistent node ('dcim', '0130_sitegroup'). Django tried to replace migration dcim.0130_sitegroup with any of [dcim.0003_squashed_0130] but wasn't able to because some of the replaced migrations are already applied.
root@c2263bc79785:/app/netbox/netbox#

Anything else I can do to get this back up and running?

[candlerb]

What version of Netbox did you start with?

Direct updates from Netbox <2.11 to Netbox >=3.0 are not supported. You must go via 2.11.x first.

[ganeshrrhce]

I have installed new Netbox version 4.0.3

[ganeshrrhce]

and taken db backup and restored in freshly installed server from existing server.

fresh Netbox Version 4.0.3
Python3.11

[ganeshrrhce]

[candlerb]

This is the last time I will reply, because it appears you are not reading what I am saying.

I gather that you are trying to upgrade from Netbox v2.5 to Netbox v4.0. You must follow these steps:

1. First you must install Netbox v2.11.12 somewhere (e.g. in a VM), restore your database within that instance, run ./upgrade.sh, and test that you have a fully functional Netbox v2.11
2. Next, you must install Netbox v3.7.8 somewhere (e.g. another VM), export from the v2.11, restore within the new instance, run ./upgrade.sh, and test that you have a fully functional Netbox v3.7
3. Finally, you can upgrade that instance to v4.0 (or install v4.0 in yet another VM and export/import the database in the same way)

There are no shortcuts. Do not pass Go. Do not collect $200.

If you are thinking about upgrading in-situ (i.e. within the same VM), I would strongly recommend against this. Whilst in principle it's possible to upgrade v2.5 to v2.11 in-situ, it's likely to break because you have such an old installation (and also there was a change from supervisord to systemd). Other large upgrades in situ are likely to break too, because the versions of Python that you need are different for different versions of Netbox, as well as higher minimum versions of Postgres and Redis. The upgrade from v3.7 to v4.0 should be OK though, as long as you installed v3.7 with modern dependencies.

But the one that you absolutely, definitely cannot do is upgrade v2.5 directly to v4.0 in one step. That's what the error about "squashed migrations" is telling you. It's saying that it depends on database changes that must have been already applied via a previous upgrade, and it doesn't know how to do them (because they've been removed from newer versions of Netbox).

I'm sorry, but I cannot explain it any more clearly than that. Good luck with your upgrade: if you need further help, please find a local Linux sysadmin who can help you implement the above steps.

[ganeshrrhce]

Thanks for the reply

[echobops]

Hmm, I'll have to check. I was doing it in an Unraid setup and am not sure what the previous version was. I spun up a new instance and am re-adding data (I only had a few test items in there). I could maybe export / import the db data? Not sure how compatible it is though.

[candlerb]

it's the same if you export/import. You still have to import it into Netbox 2.11.x, apply the migrations (./upgrade.sh), export it again, import it into your target Netbox >=3.0, and then apply migrations again.