-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
False
-
False
-
No
-
No
-
Undefined
-
No
-
Pending
-
None
-
Description of problem:
When starting a XLarge container size for JupyterHub notebook server and the cluster doesn't have the resources to accommodate the container size, user is presented with a error message that doesn't indicate what they should do next.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Log into RHODS
- Launch JupyterHub
- Select X Large container size and start server
Actual results:
Error message is displayed to the user and doesn't tell them what to do next in order to keep going.
Expected results:
Error prevention:
If resources are not available for a container size, can one of three options possibly happen:
- The container size is not be listed in the available options so the user never encounters the error or spends time starting up a server that won't start
- If the container size option has to be listed, can a better error message be displayed to the user such as "Insufficient resources to start this container size - please contact your ITO to increase resources"
- Is the user able to just increase the resources on their own if this occurs?
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Red Hat OpenShift Data Science operator version 1.0.14.
Additional info:
- duplicates
-
RHODS-335 Limit NB sizes to those that can be supported in cluster
- Closed
- is related to
-
RHODS-1492 Document common errors presented while spawning a Jupyter server
- Closed
-
RHODS-1493 Implement a "force stop" button for cases where notebook server deployment fails
- Closed