This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
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.
What does this PR do?
This is an attempt to possibly improve the situation with the recent round of APM Integration Test failures.
I have tried as many ways as I can think of to reproduce the errors, which seem to be related to the health-check for the Kibana container failing on start. I've run it locally, run it on the same type of Jenkins worker instance, and at no point have I been able to reproduce the 5-minute timeouts that we've been seeing.
We've also reported this problem to Kibana, and they also cannot seem to replicate it.
The only theory I really have at this point is that perhaps there is something specific in our health-check that is causing the issue, like perhaps cURL is getting the socket half-open and the health-check is just hanging.
This PR introduces a few means of trying to prevent that case from happening:
Why is it important?
Trying to get our ITs back online.