Errors when upgrading from 3.4.3 to 3.7.1 ( Migration account.0001_initial is applied before its dependency users.0004_netboxgroup_netboxuser) #14929
Replies: 3 comments 14 replies
-
I can confirm that migrating from v3.4.3 to v3.7.1 works as expected. You don't say exactly how you're creating the database; I suspect you're attempting to load data into a partially-created database rather than a new one. The new database must be completely empty when loading the v3.4.3 dump. |
Beta Was this translation helpful? Give feedback.
-
I have found some tutorials to manually migrate, but none worked as expected. Do you know a clean way to manually migrate |
Beta Was this translation helpful? Give feedback.
-
Ok the issue was related to the relocation of the admin UI views on the version 3.6: https://github.com/netbox-community/netbox/releases/tag/v3.6.0 The migration of the new account app depends on the users app. So, as the migration was already done (as show before), this could not work. I had to manually comment the dependency and run the migration again:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Deployment Type
Self-hosted
NetBox Version
v3.7.1
Python Version
3.9
Steps to Reproduce
We have 2 instances, one prod with Netbox 3.4.3 and postgesql 13 and one test with Netbox 3.7.1 and postgesql 15. We are trying to upgrade from the prod to the test instance:
Prod instance (Netbox 3.4.3 with postgesql v13):
Test instance (Netbox 3.7.1 with postgesql v15):
Expected Behavior
Migrate Netbox from 3.4.3 (postgesql v13) to 3.7.1 (postgesql v15)
Observed Behavior
Beta Was this translation helpful? Give feedback.
All reactions