Merge pull request #62142 from nikhiljindal/fixIPLeak

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Fixing ip address leak in kubemci e2e tests by always cleaning up cloud resources

Updating AfterEach in kubemci e2e tests to always call CleanupGCEIngressController, even when the ingress has already been deleted.
This is required to delete the IP address.
Our e2e tests are failing right now due to leaking IP addresses: https://k8s-testgrid.appspot.com/sig-multicluster-kubemci#kubemci-ingress-conformance

Relevant log:
https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubemci-ingress-conformance/1085/build-log.txt
```
W0403 17:45:06.821] 2018/04/03 17:45:06 main.go:299: Something went wrong: encountered 1 errors: [Error: 2 leaked resources
W0403 17:45:06.821] [ addresses ]
W0403 17:45:06.821] +NAME                                          REGION  ADDRESS         STATUS
W0403 17:45:06.822] +kubemci-edf6f1d1-3761-11e8-bd10-0a580a3c52c2          35.201.100.224  RESERVED]
```

cc @G-Harmon @nicksardo @MrHohn 

```release-note
NONE
```
This commit is contained in:
Kubernetes Submit Queue 2018-04-04 19:49:58 -07:00 committed by GitHub
commit 1966e24c02
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -597,10 +597,10 @@ var _ = SIGDescribe("Loadbalancing: L7", func() {
}
if jig.Ingress == nil {
By("No ingress created, no cleanup necessary")
return
} else {
By("Deleting ingress")
jig.TryDeleteIngress()
}
By("Deleting ingress")
jig.TryDeleteIngress()
By("Cleaning up cloud resources")
Expect(gceController.CleanupGCEIngressController()).NotTo(HaveOccurred())