Check that kube-dns is healthy before running tests #1260
Merged
Conversation
This file contains 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
andresmgot
changed the title
absoludity
approved these changes
Oct 30, 2019
script/e2e-test.sh
Outdated
| # Wait for Kubeapps Jobs | ||
| k8s_wait_for_job_completed kubeapps apprepositories.kubeapps.com/repo-name=stable | ||
| echo "Job apprepositories.kubeapps.com/repo-name=stable ready" | ||
|
|
||
| echo "All deployments ready. PODs:" | ||
| kubectl get pods -n kubeapps -o wide | ||
|
|
||
| # DEBUG |
There was a problem hiding this comment.
Did you mean to leave this in?
There was a problem hiding this comment.
nope, I forgot to send the last commit cleaning up
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The goal of this PR is to avoid errors like https://circleci.com/gh/kubeapps/kubeapps/11173
I have added a check that waits for all the endpoints to be ready before running the tests. Additionaly, I have added a retry so if the first test execution fails, it retries once.
Last 7 executions of the tests don't present that issue so this should be fixed.