Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
…8508) # Backport This will backport the following commits from `main` to `8.13`: - [[Fleet] Add retry logic to serverless API check (#176808)](#176808) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2024-02-21T09:14:10Z","message":"[Fleet] Add retry logic to serverless API check (#176808)\n\n## Summary\r\n\r\nCloses #176352 #176399 added the possibility to\r\nconfigure new Fleet Server hosts in serverless, with the constraint that\r\nthe host URL must match the default URL. The API integration tests\r\nwritten to test this have been flaky, due to failure retrieving the\r\ndefault Fleet Server host or default Elasticsearch output from saved\r\nobjects. This PR adds retry in the tests.\r\n\r\nNote: I have tried adding retry logic in the API handlers but kept\r\nhitting test flakiness.\r\n\r\nThis fix has been tested using the Flaky Test Runner Pipeline, with\r\n48/49 test runs for observability and security project types:\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5218\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5222\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5225\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"83e64be5d6730ec1f22ade806192bf1eab54751a","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.14.0"],"number":176808,"url":"#176808 Add retry logic to serverless API check (#176808)\n\n## Summary\r\n\r\nCloses #176352 #176399 added the possibility to\r\nconfigure new Fleet Server hosts in serverless, with the constraint that\r\nthe host URL must match the default URL. The API integration tests\r\nwritten to test this have been flaky, due to failure retrieving the\r\ndefault Fleet Server host or default Elasticsearch output from saved\r\nobjects. This PR adds retry in the tests.\r\n\r\nNote: I have tried adding retry logic in the API handlers but kept\r\nhitting test flakiness.\r\n\r\nThis fix has been tested using the Flaky Test Runner Pipeline, with\r\n48/49 test runs for observability and security project types:\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5218\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5222\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5225\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"83e64be5d6730ec1f22ade806192bf1eab54751a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.14.0","labelRegex":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"#176808 Add retry logic to serverless API check (#176808)\n\n## Summary\r\n\r\nCloses #176352 #176399 added the possibility to\r\nconfigure new Fleet Server hosts in serverless, with the constraint that\r\nthe host URL must match the default URL. The API integration tests\r\nwritten to test this have been flaky, due to failure retrieving the\r\ndefault Fleet Server host or default Elasticsearch output from saved\r\nobjects. This PR adds retry in the tests.\r\n\r\nNote: I have tried adding retry logic in the API handlers but kept\r\nhitting test flakiness.\r\n\r\nThis fix has been tested using the Flaky Test Runner Pipeline, with\r\n48/49 test runs for observability and security project types:\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5218\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5222\r\n🟢\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5225\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"83e64be5d6730ec1f22ade806192bf1eab54751a"}}]}] BACKPORT-->
- Loading branch information