Migration from Old Version #995
Unanswered
pts-jeffreyjewitt
asked this question in
Getting Help
Replies: 3 comments 6 replies
-
We are aware that the DB might be unrecoverable. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please read all release notes from Netbox. You can't directly upgrade to the newest version. You have to go to version 2.11.x first. |
Beta Was this translation helpful? Give feedback.
5 replies
-
Managed to upgrade from 2.6.x to release using this process:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Current Behavior
Trying to upgrade to version 3.4.8 from a version (unknown 2.x.x).
After importing the DB, getting this error:
netbox-docker-netbox-1 | ⏳ Waiting on DB... (3s / 30s)
netbox-docker-netbox-1 | 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.
netbox-docker-netbox-1 | [ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
netbox-docker-netbox-1 | ⏳ Waiting on DB... (6s / 30s)
netbox-docker-netbox-1 | 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.
netbox-docker-netbox-1 | [ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
netbox-docker-netbox-1 | ⏳ Waiting on DB... (9s / 30s)
netbox-docker-netbox-1 | 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.
netbox-docker-netbox-1 | [ Use DB_WAIT_DEBUG=1 in netbox.env to print full traceback for errors here ]
netbox-docker-netbox-1 | ⏳ Waiting on DB... (12s / 30s)
Is there a way to force the DB migrations to complete?
Thanks
Expected Behavior
Import data, that it takes the data and migrates it
Docker Compose Version
Docker Compose version v2.3.3
Docker Version
The git Revision
61a3afb
The git Status
Startup Command
docker compose up / docker compose start
NetBox Logs
Content of docker-compose.override.yml
Beta Was this translation helpful? Give feedback.
All reactions