test: Increase timeout for waiting LB IP addr on GKE#13557
Merged
Conversation
Recently, the test case which waits for LB IP addr started to fail:
github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Cannot retrieve loadbalancer IP for test-lb
Expected
<*errors.errorString | 0xc000324af0>: {
s: "could not get service LoadBalancer IP addr: 30s timeout expired",
}
to be nil
github.com/cilium/cilium/test/k8sT/Services.go:920
This happens because on GKE we use GCP LB which provisioning might take longer
than 30s. For now, let's increase the timeout. If it doesn't help, we can
always install dummy-lb instead.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
Member
Author
|
retest-gke |
nebril
approved these changes
Oct 14, 2020
pchaigno
approved these changes
Oct 14, 2020
Member
|
gke tests, which were affected, passed. this won't affect other builds, will merge soon |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recently, the test case which waits for LB IP addr started to fail:
This happens because on GKE we use GCP LB which provisioning might take longer
than 30s. For now, let's increase the timeout. If it doesn't help, we can
always rely on dummy-lb instead.
Fix #13554