-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Make waiting for Host configurable via --wait-timeout flag #8948
Conversation
Signed-off-by: Pablo Caderno <[email protected]>
Hi @kadern0. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kadern0 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Travis tests have failedHey @kadern0, 1st Buildmake test
TravisBuddy Request Identifier: 4f1de570-dad5-11ea-bee2-571e9d389dd6 |
Can one of the admins verify this patch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this PR is doing the right thing by increasing the startHost timeout as I seen it in sometimes time out for hyperv in nested virtualization.
but I would like this to use the same flag
--wait-timeout so basically that would be the Max Wait for everything minikube waits on
Start Host or Kubernetes components
Set default value if not specified by the user. Signed-off-by: Pablo Caderno <[email protected]>
Signed-off-by: Pablo Caderno <[email protected]>
Travis tests have failedHey @kadern0, 1st Buildmake test
TravisBuddy Request Identifier: c2a61f70-dbb2-11ea-bc40-19e33457b5db |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR
Signed-off-by: Pablo Caderno [email protected]
@sharifelgamal can you have a look at this?
would close this #8961