ModuleNotFoundError: No module named 'graphql.version' error on 4.5.2 upgrade to later 4.5 releases #22225
-
|
Anyone seen failure upgrading from 4.5.2 to anything higher in the 4.5.X releases regarding graphql.version when the migration step is executed: Applying database migrations (python3 netbox/manage.py migrate)... I've removed all but the netbox_branching plugin from my local_requirements and configuration.py. Checked and I see /graphql/version.py under site packages. Any thoughts appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
This looks like an import-path or package-version mismatch rather than NetBox failing to find a file that is definitely on the active Python path.
/opt/netbox-4.5.3/venv/bin/python -c "import graphql, sys; print(graphql.__file__); print(getattr(graphql, '__path__', None)); print(sys.path)"
/opt/netbox-4.5.3/venv/bin/python -m pip show graphql graphql-core strawberry-graphql strawberry-graphql-djangoThings I would look for:
If The cleanest test is usually a fresh venv for 4.5.3/4.5.x, then install NetBox's pinned requirements and only add |
Beta Was this translation helpful? Give feedback.
Traced this down to an issue in configuration.py. Didn't affect 4.5.2 but seemed to have caused issues with 4.5.3 and above. Rebuilt configuration.py from the supplied example and no issues showing up during ./upgrade.sh execution. Again appreciate the work in that reply.