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

add environment diagnostics #39

Open
4 tasks
BenTheElder opened this issue Sep 26, 2018 · 7 comments
Open
4 tasks

add environment diagnostics #39

BenTheElder opened this issue Sep 26, 2018 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. 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.
Milestone
1.0

Comments

@BenTheElder
Copy link
Member

BenTheElder commented Sep 26, 2018 •
edited
Loading

we should have a number of checks when kind fails, to help diagnose issues in the environment, ideally this can also be invoked by another command, some rough ideas:

  • check if there are existing containers tagged with the current cluster when creating
  • more gracefully handle lack of cluster artifacts when deleting
  • gracefully handle incompatible docker / lack of docker
  • base image builds should check that go exists

/priority important-soon
@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 26, 2018
@BenTheElder BenTheElder added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 27, 2018
This was referenced Oct 3, 2018
Closed
Merged
Closed
@BenTheElder BenTheElder mentioned this issue Oct 23, 2018
Merged
@BenTheElder
Copy link
Member Author

/assign
The "cluster already exists" / "no cluster exists" for create and delete would be nice to get into our first release.

@BenTheElder
Copy link
Member Author

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Nov 15, 2018
@BenTheElder BenTheElder added this to the 2018 Goals milestone Dec 8, 2018
@BenTheElder BenTheElder modified the milestones: 2018 Goals, 2019 goals Jan 3, 2019
@BenTheElder BenTheElder removed the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Jan 31, 2019
@BenTheElder
Copy link
Member Author

this work is now stale, will come back to it later

@BenTheElder
Copy link
Member Author

I beleive @neolit123 added the "existing cluster name" check

@BenTheElder BenTheElder modified the milestones: 2019 goals, 1.0 Feb 11, 2019
@alejandrox1
Copy link
Contributor

haven't been participating as much as I'd like to but i'd like to get back to a more regular workflow and start working on this. I'll get something for handling incompatible/lack of docker 🙂

@BenTheElder BenTheElder mentioned this issue May 31, 2019
Closed
zegl added a commit to zegl/kind that referenced this issue Jun 2, 2019
@zegl
Add a preflight check that asserts docker connectivity
35b2c26 
Assert that the docker daemon is running, and that we're able to connect to it.
This is done by executing 'docker ps', and checking the exit code.

This updates kubernetes-sigs#39
This fixes kubernetes-sigs#554
@zegl zegl mentioned this issue Jun 2, 2019
Closed
@BenTheElder BenTheElder changed the title add preflight checks add environment diagnostics Jun 3, 2019
@aojea
Copy link
Contributor

aojea commented Jun 21, 2019

@BenTheElder please add a check for IPv6 if IPfamily with IPv6 to the list😅
it took me 30 mins to realize it was failing because the docker daemon didn´t have IPv6 enabled

@BenTheElder BenTheElder mentioned this issue Jul 21, 2019
Closed
@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 Sep 19, 2019
@kubernetes-sigs kubernetes-sigs deleted a comment from fejta-bot Sep 19, 2019
@BenTheElder BenTheElder removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 19, 2019
@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 Dec 18, 2019
@BenTheElder BenTheElder added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 20, 2019
@kubernetes-sigs kubernetes-sigs deleted a comment from fejta-bot Dec 20, 2019
@BenTheElder BenTheElder added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 25, 2021
@BenTheElder BenTheElder removed their assignment Jul 29, 2021
@stmcginnis
Copy link
Contributor

Another possible check - we've had some issues due to DOCKER_DEFAULT_PLATFORM being set. Could include a check for that as a data point when collecting troubleshooting data.

Another common issue could be helped with collecting any available Docker/Docker Desktop information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. 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
1.0
Development

No branches or pull requests
5 participants
@BenTheElder @stmcginnis @aojea @alejandrox1 @k8s-ci-robot