-
Notifications
You must be signed in to change notification settings - Fork 797
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
Starting user server fails with 500 Internal Server Error after removing profileList #3297
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Forgot to note that I've also tried |
Also tried restarting all the JupyterHub deployments - same result. kubectl rollout restart deployment hub
kubectl rollout restart deployment user-scheduler
kubectl rollout restart deployment proxy Exec'ing into the hub container confirms the user-specific leftover profile configuration jovyan@hub-c5445f467-7vvpb:/srv/jupyterhub$ sqlite3 /srv/jupyterhub/jupyterhub.sqlite
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> SELECT * FROM spawners ;
1|1||{"pod_name": "jupyter-taylor-20braun-2djones", "namespace": "computeapi", "dns_name": "jupyter-taylor-20braun-2djones.computeapi.svc.cluster.local"}|||2023-12-08 18:55:21.032237|{"profile": "standard-environment"}|
2|5|1|{"pod_name": "jupyter-labuser", "namespace": "computeapi", "dns_name": "jupyter-labuser.computeapi.svc.cluster.local"}||2023-12-08 18:48:19.144022|2023-12-08 19:36:27.935000||jupyterhub-user-labuser
3|2|||||||
4|3|||||||
5|4||||||| |
Workaround is: UPDATE spawners SET user_options = NULL; then restart the hub deployment: |
Bug description
I started with a working multi-profile installation with a few profiles like:
I then deleted the entire
profileList
(no longer want users to have the option of different environments). Now when I try to login and start a singleuser server I get "500 : Internal Server Error". I tested with another user account who had never previously logged in to the multi-profile deployment that worked.From the logs (see below) it's clear that JupyterHub is remembering the
standard-environment
slug corresponding to the the first profile I had previously in the multi-profile configuration.How to reproduce
See explanation above.
Expected behaviour
Expected that users who had logged in previously would still be able to start their singleuser server.
Your personal set up
Z2JH in AWS. Kubernetes version 1.28.
kubectl logs hub-...
The text was updated successfully, but these errors were encountered: