v2.8.6 -> 3.1 - 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. #8966
-
NetBox versionv2.8.6 Python version3.7 Steps to ReproduceUpgrade Python 3.6.9 -> 3.9
Confirmed running Postgresql 10
Confirm Redis version
Move old 2.8.6 version to a new folder
Create an empy folder
Download latest NetBox
Copy over settings/configs
Run Upgrade
--- LOG Using Python 3.9.12 The above exception was the direct cause of the following exception: Traceback (most recent call last): Expected BehaviorNetbox was expected to be upgraded. Observed BehaviorAfter running upgrade and generating error Server Error The complete exception is provided below: <class 'django.contrib.contenttypes.models.ContentType.DoesNotExist'> ContentType matching query does not exist. Python version: 3.9.12 |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
just after ive posted this i found a reference that i need to upgrade to v2.11 before going to v3.. will try that first and update |
Beta Was this translation helpful? Give feedback.
-
Downloaded v2.11 Showed an error, not sure what to make of it: Creating a new virtual environment at /opt/netbox/venv... Now frontend shows: 502 Bad Gateway after a reboot. |
Beta Was this translation helpful? Give feedback.
-
i guess next step is to upgrade each individual version ? |
Beta Was this translation helpful? Give feedback.
-
issue resolved; by manually editing the upgrade.sh to bypass the virtual environment checks i was able to install to v 2.10, i was then abe to upgrade normally to v2.11.12. |
Beta Was this translation helpful? Give feedback.
-
I'm not quite sure that would be the appropriate solution. I was running into the same error deploying a new instance of Netbox 2.10.10 (testing backwards compatibility, not for actually using it). I used a pip constraints file (passed to the For reference: pallets/markupsafe#284 |
Beta Was this translation helpful? Give feedback.
issue resolved; by manually editing the upgrade.sh to bypass the virtual environment checks i was able to install to v 2.10, i was then abe to upgrade normally to v2.11.12.
changing to Python 3.7, i had to resetup PIP and then was able to upgrade without issue