github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-01 07:47:56 +00:00
Code Issues Projects Releases Wiki Activity

e2e: For AWS, tolerate an LB change when the service changes

Browse Source 
We have an issue to track the problem: #11002

The test was serving as a reminder that this needed fixing, but
for v1 we should just test what we expect to happen.
This commit is contained in:
Justin Santa Barbara 2015-07-09 13:31:30 -04:00
parent d864d271af
commit 627261082c
1 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
test/e2e/service.go
View File

@ -448,8 +448,20 @@ var _ = Describe("Services", func() {
Failf("got unexpected len(Status.LoadBalancer.Ingresss) for NodePort service: %v", service)
}
ingress2 := service.Status.LoadBalancer.Ingress[0]
// TODO: This is a problem on AWS; we can't just always be changing the LB
Expect(ingress1).To(Equal(ingress2))
// TODO: Fix the issue here: https://github.com/GoogleCloudPlatform/kubernetes/issues/11002
if providerIs("aws") {
// TODO: Make this less of a hack (or fix the underlying bug)
time.Sleep(time.Second * 120)
service, err = waitForLoadBalancerIngress(c, serviceName, ns)
Expect(err).NotTo(HaveOccurred())
// We don't want the ingress point to change, but we should verify that the new ingress point still works
ingress2 = service.Status.LoadBalancer.Ingress[0]
Expect(ingress1).NotTo(Equal(ingress2))
} else {
Expect(ingress1).To(Equal(ingress2))
}
By("hitting the pod through the service's updated NodePort")
testReachable(ip, nodePort2)