-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Bug 2090816: Increase bootstrap timeout, not k8s API timeout #6010
Conversation
This fixes a previous change where we mistakenly increased the Kubernetes API timeout instead of the bootstrap timeout.
@honza: This pull request references Bugzilla bug 2090816, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@honza: This pull request references Bugzilla bug 2090816, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
/lgtm
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@honza: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@honza: All pull requests linked via external trackers have merged: Bugzilla bug 2090816 has been moved to the MODIFIED state. In response to this:
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. |
/cherrypick release-4.10 |
@honza: #6010 failed to apply on top of branch "release-4.10":
In response to this:
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. |
Hello folks! @honza @derekhiggins, wanted to pay your attention that the higher timeout needed not only for
but for all platforms where BM instances used. AFAIU its +1 extra case at the current moment - its AWS metal instances. And that's exact our problem =( It would be awesome if you find some time to provide a fix for such case :) thanks in advance and have a great day! |
This fixes a previous change where we mistakenly increased the
Kubernetes API timeout instead of the bootstrap timeout.