Netbox UI is throwing Module Not found Error #14990
-
Hi Team , Urgent help required. I recently added the self signed certificate to run the netbox on https .Netbox is working in docker container on https, Server Error Missing required packages. This installation of NetBox might be missing one or more required Python packages. These packages are listed in requirements.txt and local_requirements.txt, and are normally installed as part of the installation or upgrade process. To verify installed packages, run pip freeze from the console and compare the output to the list of required packages. WSGI service not restarted after upgrade. If this installation has recently been upgraded, check that the WSGI service (e.g. gunicorn or uWSGI) has been restarted. This ensures that the new code is running. The complete exception is provided below: <class 'ModuleNotFoundError'> No module named 'no' Python version: 3.10.12 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 8 replies
-
It sounds like you have a typo somewhere, search your code for the word |
Beta Was this translation helpful? Give feedback.
-
![]() |
Beta Was this translation helpful? Give feedback.
-
If you're running in minikube, then where did you get the YAML resource definitions from? Can you show them? I suspect there is a bug in them. Beware YAML with values like true, false, yes, no. If you don't quote them then they may be treated as booleans (*). Since your error message involves the string "no" then I suspect this might be what's going on. You can set environment variable DEBUG to "true" using standard kubernetes mechanisms. This should show you the full backtrace within the web UI, which will identify the exact line of python code which is problematic. Again, make sure the value is quoted in YAML.
(*) This was changed in YAML 1.2 to be only "true" or "false". However there are still many YAML 1.1 parsers out there. |
Beta Was this translation helpful? Give feedback.
"The helm template" - which helm template?? This must be some third-party creation, and a quick Google turns up many of them, so you should be specific about which one.
In any case, the problems you have deploying Netbox using it would be best raised with the creator of that helm template, not with the Netbox project itself.
As before: you could set DEBUG=true and get a backtrace for this error.
But again, since you've already found that Netbox deploys successfully using docker-compose, your problem is still with the Helm chart or how you're using it - not with Netbox itself or the published do…