Skip to content
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

Error spawning JH Server #90

Closed
oindrillac opened this issue Feb 15, 2021 · 9 comments
Closed

Error spawning JH Server #90

oindrillac opened this issue Feb 15, 2021 · 9 comments
Labels
human_intervention_required to a human team mate! kind/bug Categorizes issue or PR as related to a bug. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@oindrillac
Copy link
Member

Describe the bug
I tried to stop my server and on restarting it, it is stuck on the spawn screen and timed out twice.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://jupyterhub-opf-jupyterhub.apps.cnv.massopen.cloud/hub/home'
  2. Click on 'Stop Server'
  3. Now Spawn a new server and select 's2i-minimal' image and 'Large' size.
  4. Spawn Fails and times out
  5. Click 'Relaunch Server'
  6. Spawn Fails again

Expected behaviour
The JH notebook server should have spawned succesfully

Screenshots

image

image

@goern
Copy link
Member

goern commented Feb 16, 2021

/kind bug
/sig devops

@sesheta sesheta added kind/bug Categorizes issue or PR as related to a bug. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. labels Feb 16, 2021
@sefkhet-abwy sefkhet-abwy bot added the human_intervention_required to a human team mate! label Feb 16, 2021
@tumido tumido added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Feb 16, 2021
@tumido
Copy link
Member

tumido commented Feb 16, 2021

Thank you for raising this ticket! We're facing some issues with OpenShift networking and pod scheduling. https://github.com/operate-first/SRE/issues/62

This issue is caused by this problem, therefore I'm gonna mark this issue as duplicate though I'm gonna keep it open and pin it for visibility.

@tumido tumido pinned this issue Feb 16, 2021
@oindrillac
Copy link
Member Author

Update on this: I still see an issue spawning my NB Server with my existing RH account. I re-spawned and tried logging out during the long spawn process to sign back in with my external personal account and it spawned fine for me with the external account 👍

@tumido
Copy link
Member

tumido commented Feb 17, 2021

May be related: #91

@cfchase cfchase unpinned this issue Feb 26, 2021
@oindrillac
Copy link
Member Author

oindrillac commented Mar 1, 2021

My MOC JH Account is still having issues while spawning. It times out trying to spawn each time. Is this still expected?
I am currently using JH with my external personal account which spawns fine but has only 2 Gigs PVC and hence is a blocker for my work.

image

@tumido tumido pinned this issue Mar 1, 2021
@tumido
Copy link
Member

tumido commented Mar 2, 2021

@oindrillac it's spawning just fine for my account right now and I'm unable to find any logs on your failure. Wanna ping me once you're online today and we can try sorting it out? 🙂

@HumairAK
Copy link
Member

HumairAK commented Mar 2, 2021

I see that a PR was made w.r.t to this -- was the issue resolved?

@tumido
Copy link
Member

tumido commented Mar 3, 2021

I wouldn't say resolved, the PR is rather a workaround. @oindrillac's original user profile is still not usable and I couldn't figure out why. I've decided it's not worth fixing, because it would eventually be resolved by the cluster reinstall.

I think this issue may be closed as a wontfix (?) probably. WDYT?

@oindrillac
Copy link
Member Author

This was fixed with the cluster reprovisioning 🎉 closing :)

@tumido tumido unpinned this issue Mar 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
human_intervention_required to a human team mate! kind/bug Categorizes issue or PR as related to a bug. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

5 participants