[package testing] Stabilize status api test #129228
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
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry.
jbudz
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
spalger
approved these changes
Apr 1, 2022
kibanamachine
pushed a commit
that referenced
this pull request
Apr 1, 2022
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry. (cherry picked from commit f265480)
kibanamachine
pushed a commit
that referenced
this pull request
Apr 1, 2022
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry. (cherry picked from commit f265480)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Apr 1, 2022
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry. (cherry picked from commit f265480) Co-authored-by: Jonathan Budzenski <jon@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Apr 1, 2022
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry. (cherry picked from commit f265480) Co-authored-by: Jonathan Budzenski <jon@elastic.co>
jbudz
added a commit
that referenced
this pull request
Apr 6, 2022
There appears to be a brief moment after kibana starts where we are listening for http connections but immediately closing requests to the status API. The return code by ansible here is -1, so this adds that as a valid response to retry.
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.
There appears to be a brief moment after kibana starts where we are
listening for http connections but immediately closing requests to the
status API. The return code by ansible here is -1, so this adds that as
a valid response to retry.
@elastic/kibana-core FYI. https://buildkite.com/elastic/kibana-package-testing/builds?branch=main - starting failing on March 26th.