Upgrade Issue from NetBox 3.6 to 4.0: Missing 'users_user' Relation in Database

[alemsas]

Hello NetBox Community,

I'm in the process of upgrading from NetBox version 3.6 to 4.0, and I'm encountering a database migration issue upon restoring my database from the older version and attempting to log into the new setup. I am running this on Python 3.11.6, with no plugins installed.

**Error Message:**
<class 'django.db.utils.ProgrammingError'>
relation "users_user" does not exist
LINE 1: ...ser"."is_active", "users_user"."date_joined" FROM "users_use...

This error occurs when I attempt to log into the NetBox web interface, suggesting that the 'users_user' table is missing from the database.

netbox=# \conninfo
You are connected to database "netbox" as user "netbox" on host "x.x.x.x" at port "5432".

also for netbox container

docker logs -f --tail=50 netbox-docker-netbox-1
Skipping config initialization (database unavailable)
172.25.0.1 - - [09/May/2024:15:00:55 +0000] "POST /login/ HTTP/1.0" 500 2358 "https://assetkade-idc.arvaninternal.ir/login/?next=/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0"
172.25.0.1 - - [09/May/2024:15:00:55 +0000] "GET /static/netbox-light.css HTTP/1.0" 200 233661 "https://assetkade-idc.arvaninternal.ir/login/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0"
Skipping config initialization (database unavailable)
172.25.0.1 - - [09/May/2024:15:00:55 +0000] "GET /favicon.ico HTTP/1.0" 404 9121 "https://assetkade-idc.arvaninternal.ir/login/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:00:56 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:01:11 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:01:26 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:01:42 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:01:57 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:02:12 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:02:27 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:02:42 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:02:57 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:03:12 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:03:27 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:03:43 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:03:58 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:04:13 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
Skipping config initialization (database unavailable)
::1 - - [09/May/2024:15:04:28 +0000] "GET /api/ HTTP/1.1" 200 549 "-" "curl/8.2.1"
2024/05/09 15:04:39 [notice] 7#7 process 315 exited with code 0
🧬 loaded config '/etc/netbox/config/configuration.py'
🧬 loaded config '/etc/netbox/config/extra.py'
🧬 loaded config '/etc/netbox/config/logging.py'
🧬 loaded config '/etc/netbox/config/plugins.py'
🧬 loaded config '/etc/netbox/config/configuration.py'
🧬 loaded config '/etc/netbox/config/extra.py'
🧬 loaded config '/etc/netbox/config/logging.py'
🧬 loaded config '/etc/netbox/config/plugins.py'
2024/05/09 15:04:39 [notice] 7#7 process 316 exited with code 0
2024/05/09 15:04:40 [notice] 319#319 app process 406 exited with code 0
2024/05/09 15:04:40 [alert] 319#319 sendmsg(13, -1, -1, 2) failed (32: Broken pipe)
2024/05/09 15:04:40 [notice] 319#319 app process 451 exited with code 0
2024/05/09 15:04:40 [alert] 319#319 sendmsg(13, -1, -1, 2) failed (32: Broken pipe)
2024/05/09 15:04:40 [notice] 7#7 process 319 exited with code 0
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0183_devicetype_exclude_from_utilization depends on nonexistent node ('dcim', '0182_zero_length_cable_fix'). Django tried to replace migration dcim.0182_zero_length_cable_fix with any of [dcim.0167_squashed_0182] but wasn't able to because some of the replaced migrations are already applied.
[ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
⏳ Waiting on DB... (0s / 30s)
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0183_devicetype_exclude_from_utilization depends on nonexistent node ('dcim', '0182_zero_length_cable_fix'). Django tried to replace migration dcim.0182_zero_length_cable_fix with any of [dcim.0167_squashed_0182] but wasn't able to because some of the replaced migrations are already applied.
[ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
⏳ Waiting on DB... (3s / 30s)
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0183_devicetype_exclude_from_utilization depends on nonexistent node ('dcim', '0182_zero_length_cable_fix'). Django tried to replace migration dcim.0182_zero_length_cable_fix with any of [dcim.0167_squashed_0182] but wasn't able to because some of the replaced migrations are already applied.
[ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
⏳ Waiting on DB... (6s / 30s)

Steps I've Taken:

1. Restored the database from a backup of NetBox 3.6.
2. Checked the user app's migrations folder, which contains only 0001_initial.py and __init__.py.
3. Tried running ./manage.py sqlmigrate user 0001_initial to understand what is being applied, but the issue persists.

Questions:

1. Are there specific migrations or additional steps required to ensure database compatibility when upgrading from 3.6 to 4.0?
2. How can I resolve the missing 'users_user' relation error? Is there a known issue with this migration path?
3. Should I manually trigger any migrations to align the database schema with NetBox 4.0 requirements?

I would greatly appreciate any advice or insights into how to successfully transition my database to work with NetBox 4.0. Thank you in advance for your support!

[candlerb]

Restored the database from a backup of NetBox 3.6.

You need to upgrade to 3.7.8, before you can update to 4.0. This is because it's a major version increment

[alemsas]

Is it correct if I have a database from version 3.6 and now I directly install Netbox version 4 on a new machine?
Is there a guide for updating Docker?

[candlerb]

Is it correct if I have a database from version 3.6 and now I directly install Netbox version 4 on a new machine?

No. If you're exporting to a new machine running 4.0 then you'll first have to upgrade to 3.7 in-situ, then export and use this export to go into the 4.0 machine (where you would then run upgrade.sh after restoring the dump).

Or you could do it in two stages: export the 3.6 into a new machine running 3.7, run upgrade.sh, and repeat the process (export from 3.7, import into a 4.0 machine, run upgrade.sh)

It may also be possible to upgrade from 3.7 to 4.0 in-situ, but riskier, given that the underlying dependencies have changed, especially the minimum python version.

Docs:

• https://docs.netbox.dev/en/stable/administration/replicating-netbox/
• https://docs.netbox.dev/en/stable/installation/upgrading/

Is there a guide for updating Docker?

There is a wiki at https://github.com/netbox-community/netbox-docker/wiki

I believe that you'd first deploy/run a netbox 3.7 container (which will update the database to the 3.7 schema), and once that's working, deploy/run a 4.0 container.