[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive #222691
Conversation
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
This test has failed a few times recently with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur.
rylnd
added
release_note:skip
Contributor
|
Pinging @elastic/security-detection-engine (Team:Detection Engine) |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8329[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/detection_engine/alerts/trial_license_complete_tier/configs/ess.config.ts: 200/200 tests passed. |
Contributor
💚 Build Succeeded
Metrics [docs]
cc @rylnd |
nkhristinin
approved these changes
Jun 5, 2025
rylnd
added
backport:all-open
Contributor
|
Starting backport for target branches: 7.17, 8.17, 8.18, 8.19, 9.0 https://github.com/elastic/kibana/actions/runs/15476199813 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 5, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 7fe71b3)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 5, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 7fe71b3)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 5, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 7fe71b3)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 5, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 7fe71b3)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jun 5, 2025
…re loading our alerts archive (#222691) (#222893) # Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)](#222691) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-06-05T20:05:06Z","message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Detection Engine","8.19 candidate","v9.1.0"],"title":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive","number":222691,"url":"https://github.com/elastic/kibana/pull/222691","mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222691","number":222691,"mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Jun 5, 2025
…ore loading our alerts archive (#222691) (#222892) # Backport This will backport the following commits from `main` to `8.19`: - [[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)](#222691) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-06-05T20:05:06Z","message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Detection Engine","8.19 candidate","v9.1.0"],"title":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive","number":222691,"url":"https://github.com/elastic/kibana/pull/222691","mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222691","number":222691,"mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Jun 5, 2025
…ore loading our alerts archive (#222691) (#222890) # Backport This will backport the following commits from `main` to `8.17`: - [[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)](#222691) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-06-05T20:05:06Z","message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Detection Engine","8.19 candidate","v9.1.0"],"title":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive","number":222691,"url":"https://github.com/elastic/kibana/pull/222691","mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222691","number":222691,"mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Jun 5, 2025
…ore loading our alerts archive (#222691) (#222891) # Backport This will backport the following commits from `main` to `8.18`: - [[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)](#222691) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-06-05T20:05:06Z","message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Detection Engine","8.19 candidate","v9.1.0"],"title":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive","number":222691,"url":"https://github.com/elastic/kibana/pull/222691","mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222691","number":222691,"mergeCommit":{"message":"[Detection Engine][Test Fix] Ensure that alerts are absent before loading our alerts archive (#222691)\n\n## Summary\n\nThis test has [failed a few times\nrecently](#219112) with a\n`version_conflict_engine_exception`, stating explicitly that the\ndocuments we're trying to load already exist in elasticsearch. In one\ncase the reason was obvious (the suite was retried), but in another it\nwas not clear why the data was there to cause this exception.\n\nRegardless, adding this sanity check (deleting all the alerts) should\nensure that this behavior does not recur.\n\nCloses #219112.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329))\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7fe71b3f4ee4b68e22bb424aa7b8ccc2e3c40f1a"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <[email protected]>
pmuellr
pushed a commit
to pmuellr/kibana
that referenced
this pull request
Jun 11, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Jun 12, 2025
…ding our alerts archive (elastic#222691) ## Summary This test has [failed a few times recently](elastic#219112) with a `version_conflict_engine_exception`, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception. Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur. Closes elastic#219112. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ([200x](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8329)) - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Summary
This test has failed a few times recently with a
version_conflict_engine_exception, stating explicitly that the documents we're trying to load already exist in elasticsearch. In one case the reason was obvious (the suite was retried), but in another it was not clear why the data was there to cause this exception.Regardless, adding this sanity check (deleting all the alerts) should ensure that this behavior does not recur.
Closes #219112.
release_note:*label is applied per the guidelines