e2e test fix: Wait longer when first creating ELB #44696
Conversation
On any cloud (GCE or AWS), a lag between creating the LoadBalancer and having it actually start serving traffic is expected. On AWS the lag is larger, and we weren't correctly using the longer wait on our first request. Use a longer wait period on our first request. Fix kubernetes#44695
k8s-ci-robot
added
the
cncf-cla: yes
|
This change is |
k8s-github-robot
added
size/S
|
LGTM Very cool and thanks so much for the fix! /unassign |
k8s-github-robot
added
the
approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, fejta, justinsb
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
Automatic merge from submit-queue (batch tested with PRs 42272, 44696) |
|
@justinsb: The following test(s) failed:
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
On any cloud (GCE or AWS), a lag between creating the LoadBalancer and
having it actually start serving traffic is expected. On AWS the lag is
larger, and we weren't correctly using the longer wait on our first
request.
Use a longer wait period on our first request.
Fix #44695