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

TestProxy/ConsoleWarnning fails with the none driver #4339

Closed
tstromberg opened this issue May 24, 2019 · 3 comments
Closed

TestProxy/ConsoleWarnning fails with the none driver #4339

tstromberg opened this issue May 24, 2019 · 3 comments
Assignees
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@tstromberg
Copy link
Contributor

See https://storage.googleapis.com/minikube-builds/logs/4328/Linux-None.txt

            E0523 19:42:31.881144    3045 start.go:529] StartHost: detecting provisioner: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
            I0523 19:42:31.881204    3045 utils.go:122] non-retriable error: detecting provisioner: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
            W0523 19:42:31.881310    3045 exit.go:100] Unable to start VM: detecting provisioner: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
            
            X Unable to start VM: detecting provisioner: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded

I admittedly do not understand what's going on.

@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels May 29, 2019
@tstromberg tstromberg added this to the v1.2.0-candidate milestone May 29, 2019
@medyagh
Copy link
Member

medyagh commented May 30, 2019

@tstromberg I can't replicate this on my linux box, do we have any recent PR with this failure ?

@medyagh
Copy link
Member

medyagh commented May 30, 2019

as far as the test logic, it is looking for a warning message to the user that they are using a proxy. but it minikube start doesn't get there, because it is stuck "Waiting for SSH to be available". and then it times out ... I could maybe try to increase the test time out. but I suspect it be the case, since it maxed out of the SSH tries.

@medyagh medyagh mentioned this issue May 30, 2019
@medyagh
Copy link
Member

medyagh commented Jun 5, 2019

fixed by #4383

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants