-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
Release Notes
-
Yes
-
-
-
-
-
-
Not applicable - this is provided by Intel in the OVMS operator
-
No
-
Jupyter's *Start a notebook server* page failed to start a notebook server using the OpenVINO notebook image. Intel has provided an update to the OpenVINO operator to correct this issue.
-
Documented as Resolved Issue
-
No
-
Yes
-
None
-
Critical
Description of problem:
The build of openvino is successful, but the spawning process using jupyterhub fails. Tested on 2 different clusters (4.9 and 4.11) getting the same error.
Traceback (most recent call last):
File "/opt/app-root/lib64/python3.8/site-packages/jupyterlab/labhubapp.py", line 19, in <module>
from jupyterhub.singleuser.mixins import make_singleuser_app
ModuleNotFoundError: No module named 'jupyterhub'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/app-root/bin/jupyter-labhub", line 5, in <module>
from jupyterlab.labhubapp import main
File "/opt/app-root/lib64/python3.8/site-packages/jupyterlab/labhubapp.py", line 22, in <module>
from jupyterhub.singleuser import SingleUserNotebookApp as SingleUserServerApp
ModuleNotFoundError: No module named 'jupyterhub'
Other images can be spawned without issues
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Install Openvino
- build Openvino Notebook
- Spawn openvino image using JH
Actual results:
spawning fails
Expected results:
spawining succeeds
Reproducibility (Always/Intermittent/Only Once):
reproduced on OCP 4.9, OCP 4.10 and OCP 4.11
Build Details:
Openvino operator 1.0.0
RHODS v1.13.0-6
Workaround:
Additional info:
log files attached
