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

site: Add more troubleshooting and debugging commands #9820

Open
medyagh opened this issue Dec 1, 2020 · 3 comments
Open

site: Add more troubleshooting and debugging commands #9820

medyagh opened this issue Dec 1, 2020 · 3 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@medyagh
Copy link
Member

medyagh commented Dec 1, 2020 •
edited
Loading

when someone asks how to debug a problem in minikube, we should provide all the deubbing commands we do, our current troubleshooting page doesn't have all the commands an advanced user can do

https://minikube.sigs.k8s.io/docs/handbook/troubleshooting/

we should add all the post mortem commands we do in our integration tests to our troubleshoting page

here https://github.com/medyagh/minikube/blob/2fa08942dc62c5a3c0160eb44c5a379c78797777/test/integration/helpers_test.go#L196

https://storage.googleapis.com/minikube-builds/logs/9802/da778ea/Docker_Linux.html#fail_TestSkaffold
@medyagh medyagh added kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Dec 1, 2020
@medyagh medyagh changed the title Add debugging commands website site: Add more troubleshooting and debugging commands Dec 1, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 1, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 31, 2021
@spowelljr spowelljr added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 7, 2021
@medyagh
Copy link
Member Author

medyagh commented May 5, 2021

we need to add new Troubleshooting commands to the site

including minikube logs -f debug.txt

@medyagh medyagh removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 19, 2021
@spowelljr spowelljr added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@medyagh @k8s-ci-robot @fejta-bot @spowelljr