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

delete: excessively long timeout for powering off via SSH #3695

Closed
tstromberg opened this issue Feb 16, 2019 · 0 comments
Closed

delete: excessively long timeout for powering off via SSH #3695

tstromberg opened this issue Feb 16, 2019 · 0 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@tstromberg
Copy link
Contributor

tstromberg commented Feb 16, 2019

If a minikube VM doesn't have SSH available, it takes way too long to power off -- like an entire minute or two.

We should also consider restricting this feature to hyperv, as it isn't necessary on other platforms.

@tstromberg tstromberg changed the title minikube delete: excessively long timeout for powering off via SSH delete: excessively long timeout for powering off via SSH Feb 16, 2019
@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Feb 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant