netboxDB Migration failing

[DDavidson1]

I am trying to upgrade Netbox from 3.7.8 to 4.0.0 and am now encountering an error during the migrations.

Running migrations:
Applying extras.0109_script_model...Traceback (most recent call last):
File "/data/netbox-4.0.0/venv/lib64/python3.11/site-packages/django/db/backends/utils.py", line 103, in _execute
return self.cursor.execute(sql)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/data/netbox-4.0.0/venv/lib64/python3.11/site-packages/psycopg/cursor.py", line 732, in execute
raise ex.with_traceback(None)
psycopg.errors.InsufficientPrivilege: permission denied for schema public
LINE 1: CREATE TABLE "extras_script" ("id" bigint NOT NULL PRIMARY K...
^

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

Any suggestions? I have played with grant access in PSQL, but not had any luck..

Thanks,

[markkuleinio]

Did you try this:

-- the next two commands are needed on PostgreSQL 15 and later
\connect netbox;
GRANT CREATE ON SCHEMA public TO netbox;

https://netboxlabs.com/docs/netbox/en/stable/installation/1-postgresql/#database-creation

[DDavidson1]

That fixed that problem, but now. I get an error mldocs build "AttributeError: 'dict' object has no attribute 'link_titles'".

[markkuleinio]

On a scale of 0 to 10, how sure you are that you really want to install a year-old version (4.0.0) of NetBox and try to fight with possible errors with outdated package dependencies?

Asking because there is no officially supported way to install NetBox versions other than the latest (currently 4.2.7).

[DDavidson1]

We got behind on the upgrades and I am working to upgrade to the latest 4.2 version.

[markkuleinio]

I'd strongly recommend going straight to 4.2.7, not trying to battle with 4.0.0. See https://netboxlabs.com/docs/netbox/en/stable/installation/upgrading/ for the supported upgrade path (3.7 -> 4.2.x is working).

[pheus]

I second this!

@markkuleinio - just a heads-up that the original issue actually started in a different thread: #19235. In that one, the author mentioned modifying the requirements.txt file.

[markkuleinio]

Right, so checking out v4.2.7 should overwrite the modified requirements.txt with the known correct version.

[DDavidson1]

OK, so somehow I had missed that you could go straight from 3.7 to 4.2. I thought I had to go through each minor release.