PVC name not using the escape scheme

JupyterHub Zero to JupyterHub on Kubernetes
,
1

I am upgrading the JH for k8s from version 3.3.7 to 4.2.0. I did set in config.yaml to use the old spawner scheme: c.KubeSpawner.slug_scheme = “escape”. But after upgrading, for a username like ‘mILK1986’ with capital letters, the user server is stuck in pending(it works fine with usernames only containing lowercase letters). Here is the log of the hub pod:

[I 2025-07-02 08:21:59.453 JupyterHub spawner:2931] Attempting to create pvc claim-milk1986---e486ff88, with timeout 3
[I 2025-07-02 08:21:59.460 JupyterHub spawner:2947] PVC claim-milk1986---e486ff88 already exists, so did not create new pvc.
[I 2025-07-02 08:21:59.463 JupyterHub spawner:2890] Attempting to create pod jupyter-m-49-4c-4b1986, with timeout 3
[I 2025-07-02 08:22:08.648 JupyterHub log:192] 200 GET /hub/api/ (jupyterhub-idle-culler@::1) 10.52ms
[I 2025-07-02 08:22:08.658 JupyterHub log:192] 200 GET /hub/api/users?state=[secret] (jupyterhub-idle-culler@::1) 8.61ms
[W 2025-07-02 08:22:09.408 JupyterHub base:1229] User mILK1986 is slow to start (timeout=10)

I can see that the pod name jupyter-m-49-4c-4b1986 is using the old scheme, but the pvc name claim-milk1986—e486ff88 is using the new safe scheme? Is this the reason that the server is always in pending status? Is there anything I missed in the configuration?

Thank you.

2

I am back to answer my questions. After some investigation I know what was happening. I created the user mILK1986 before using a safe scheme, so there was already a PVC for the user with the new name. JH remembered this and use it every time even I specified the escape scheme afterwards. Finally I removed the pv/pvc, as well as some clean up work in jupyterhub.sqlite, everything is running as expected. BTW, the pending problem is not caused by this but a misconfiguration of persistentVolumeClaim in c.KubeSpawner.volumes.

1 Like