-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 Error Jupyter notebook #818
Comments
instructions on customizing jupyterhub and notebook images: If you've already followed the instructions on the above link to create notebook images, create a secret with the credentials and add it to the jupyterhub serviceaccount: @jlewi Can you offer more instructions or the user practice to customize notebook images? |
Can you provide the full JupyterHub logs? |
Resolving since this issue has been inactive for a while. Please re-open if needed. |
… the task (kubeflow#818) * fix(pylint): detect failures and erros associated with the task * do not break if neither failure or failure element doesn't have message attribute * send xml files to artifacts folder to get detected by spyglass * parse all the tests to xml * path for pytest gets added from generate_xml function * Revert "path for pytest gets added from generate_xml function" This reverts commit 8be433afb7f93fa9017dad1a7870d9929c4d4e7b. * add only: path for pytest gets added from generate_xml function
* Return 503 from healthhandler when model is not ready If the model is not marked ready, then don't return 200 from health check handler, return a 503 instead so it can be used for kubernetes readiness probe * Fix lint warning
I tried to launch a jupyter notebook from a custom docker image. This failed (presumably because of permissions issues accessing the particular GCR). Now, jupyterhub keeps failing with the following error:
500 : Internal Server Error
Failed to reach your server. Please try again later. Contact admin if the issue persists.
You can try restarting your server from the home page.
The text was updated successfully, but these errors were encountered: