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.

Sign up for GitHub

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

Jump to bottom

[BUG] - JupyterHub 3 failing on Digital Ocean #1965

Closed
iameskild opened this issue Aug 30, 2023 · 1 comment · Fixed by #1991
Closed

[BUG] - JupyterHub 3 failing on Digital Ocean #1965

iameskild opened this issue Aug 30, 2023 · 1 comment · Fixed by #1991
Assignees
@iameskild
Labels
needs: investigation 🔍 Someone in the team needs to find the root cause and replicate this bug provider: Digital Ocean type: bug 🐛 Something isn't working
Milestone
2023.10.1

Comments

@iameskild
Copy link
Member

Describe the bug

Jupyterhub seems unreachable (Service Unavailable) but other services (except for dask-gateway) are available at their respective endpoints. Whats more, the hub pod logs don't seem to show anything wrong and I can run http://localhost:8081/hub/api successfully from within the running pod.

Expected behavior

JupyterHub should be running.

OS and architecture in which you are running Nebari

Deploy from MacOS

How to Reproduce the problem?

Deploy Nebari on Digital Ocean from the develop branch.

Command output

No response

Versions and dependencies used.

No response

Compute environment

Digital Ocean

Integrations

No response

Anything else?

No response
@iameskild iameskild added type: bug 🐛 Something isn't working needs: triage 🚦 Someone needs to have a look at this issue and triage labels Aug 30, 2023
@iameskild iameskild mentioned this issue Aug 30, 2023
Merged
10 tasks
@pavithraes pavithraes removed the needs: triage 🚦 Someone needs to have a look at this issue and triage label Aug 30, 2023
@pavithraes pavithraes moved this from New 📬 to Planned 💾 in 🪴 Nebari Project Management Aug 30, 2023
@pavithraes pavithraes moved this from Planned 💾 to New 📬 in 🪴 Nebari Project Management Aug 30, 2023
@pavithraes pavithraes added the needs: investigation 🔍 Someone in the team needs to find the root cause and replicate this bug label Aug 30, 2023
@iameskild
Copy link
Member Author

The network policy seems to be getting in the way. When I delete it from the cluster, I can access JupyterHub. This network policy appears to be coming from the z2jh helm chart but we have hub.networkPolicy.enabled = false and singleuser.networkPolicy.enabled = false...

@iameskild iameskild mentioned this issue Sep 8, 2023
Merged
10 tasks
@iameskild iameskild added this to the Release 2023.9.1 milestone Sep 11, 2023
@pavithraes pavithraes moved this from New 🚦 to In progress 🏗 in 🪴 Nebari Project Management Sep 11, 2023
@iameskild iameskild moved this from In progress 🏗 to In review/QA 👀 in 🪴 Nebari Project Management Sep 12, 2023
@github-project-automation github-project-automation bot moved this from In review/QA 👀 to Done 💪🏾 in 🪴 Nebari Project Management Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iameskild iameskild

Labels
needs: investigation 🔍 Someone in the team needs to find the root cause and replicate this bug provider: Digital Ocean type: bug 🐛 Something isn't working
Projects
🪴 Nebari Project Management
Archived in project
Milestone
2023.10.1
Development

Successfully merging a pull request may close this issue.

Modify JupyterHub networkPolicy to match existing policy nebari-dev/nebari
2 participants
@pavithraes @iameskild