From e7d26b3111f1095d3c0fc785d921ed6bab85cf2f Mon Sep 17 00:00:00 2001 From: Clayton Coleman Date: Thu, 13 Jun 2019 14:09:48 -0400 Subject: [PATCH] Increase load balancer timeout in test cases In a heavily contested AWS account (that was close to rate limits) it took more than 2m for the load balancer to begin accepting requests. This increases the timeout to 3m to give upgrade tests more of a chance to pass in a contentious environment. --- test/e2e/upgrades/services.go | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/test/e2e/upgrades/services.go b/test/e2e/upgrades/services.go index 93cffa1ef2c..d878f950083 100644 --- a/test/e2e/upgrades/services.go +++ b/test/e2e/upgrades/services.go @@ -67,7 +67,11 @@ func (t *ServiceUpgradeTest) Setup(f *framework.Framework) { // Hit it once before considering ourselves ready ginkgo.By("hitting the pod through the service's LoadBalancer") - jig.TestReachableHTTP(tcpIngressIP, svcPort, framework.LoadBalancerLagTimeoutDefault) + timeout := framework.LoadBalancerLagTimeoutDefault + if framework.ProviderIs("aws") { + timeout = framework.LoadBalancerLagTimeoutAWS + } + jig.TestReachableHTTP(tcpIngressIP, svcPort, timeout) t.jig = jig t.tcpService = tcpService