-
Notifications
You must be signed in to change notification settings - Fork 60
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
Interaction between batchspawner and profilespawner #24
Comments
Hi, I'm trying to update all the packages involved in my installation, and this remains an issue. Due to some other changes, I had to change my workaround to:
I really don't understand why I am encountering this issue. My setup -- ProfileSpawner offering the choice between a number of different SlurmSpawners (with different queue settings, with/without GPUs, etc) seems totally vanilla off-the-shelf exactly what it was meant for, yet out of the box, it just does not work. What gives? |
Further to this -- and maybe this should be a new issue -- I am finding that in the current versions of everything, OAuth authentication is ALSO broken by ProfilesSpawner. That is: Using ProfilesSpawner, my singleuser server is created on the compute node, but when my web browser goes to connect to the server, it gets a 404 Not found, and in the singleuser server logs,
When using SlurmSpawner directly, in the server logs I see the OAuth process going on,
while with ProfilesSpawner it does none of this. I haven't yet figured out how to fix this, but it just makes me wonder how ProfilesSpawner ever works for anyone. I'm not trying to be rude, it just seems like this is the most straightforward case and it just doesn't work, so I feel like I'm just missing something big. Thanks. |
Regarding the linked traitlets: I printed out the traits that are getting linked
Note that "port" and "server" are not among them! (related to the 404 reported by @Jon-Lillis #44 ?) |
Hi,
I'm not sure if this should be a batchspawner issue or a profilespawner issue. I have filed this batchspawner issue: jupyterhub/batchspawner#127
I have a (Slurm) BatchSpawner wrapped in a ProfileSpawner, for a typical academic compute cluster use case -- users can either start their notebook processes on the head node, or on a compute node via Slurm.
When a batchspawner worker starts up on the remote worker node, it calls an API on the hub, which goes to a batchspawner API handler. The API handler retrieves the user.spawner object, and tries to set its .current_port attribute. It is expecting that spawner object to be a BatchSpawner, but in my setup it is actually a ProfileSpawner, so it sets the .current_port on an object other than the one that the main BatchSpawner class is polling, and it eventually thinks that the remote process timed out.
I added the following to the batchspawner API handler, here https://github.com/jupyterhub/batchspawner/blob/master/batchspawner/api.py#L12 , and it works, but is ugly:
Now, it seems like a cleaner solution might be for WrapSpawner to propagate some setattr requests to its child_spawner?
Open to suggestions for a clean fix. Thanks!
The text was updated successfully, but these errors were encountered: