Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

diagnosis message on failed launches

See original GitHub issue

When a pod fails to launch, we should let the user know the causes: resources full, image pull failure, launch failure, pvc mount failure, crashed, etc. We can probably start with the event messages coming from kubctl describe pod

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

yuvipandacommented, Mar 8, 2018

Oops, sorry! It’s in SETUP.md. We should probably rename it…

On Thu, Mar 8, 2018 at 8:38 AM, Chia-liang Kao notifications@github.com wrote:

@yuvipanda https://github.com/yuvipanda hmm there isn’t much info in CONTRIBUTING.md in this repo re dev environment.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyterhub/kubespawner/issues/141#issuecomment-371544391, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB23h9pTAYsRcTkN4Jj6HCVFxLqfFXqks5tcV6agaJpZM4Sf955 .

– Yuvi Panda T http://yuvi.in/blog

1reaction

clkaocommented, Mar 8, 2018

@yuvipanda hmm there isn’t much info in CONTRIBUTING.md in this repo re dev environment.