-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing test: Rules Management - Rule Bulk Actions Integration Tests - ESS Env - Trial License.x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_bulk_actions/trial_license_complete_tier/perform_bulk_action_ess·ts - Rules Management - Rule Bulk Action API @ess perform_bulk_action - ESS specific logic should disable rules and migrate actions #196462
Comments
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
/skip |
New failure: kibana-on-merge - 8.x |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
I assigned you to this one and #196470. By the end of this week we need to figure out who can work on these. The goal is to understand if these test failures are indications of a bug - in which case we will have less than one week for fixing it for |
@banderror I created #197660 to address flakiness reported in this ticket and in #196470. It seems we might have race condition when performing bulk operations on enabled rules picked up by the task manager at the same time. I left only two functional tests with enabled rules since these tests check rule disabling. After applying my changes don't see any flakiness. |
…#197660) **Closes: elastic#196470 **Closes: elastic#196462 ## Summary This PR unskips `perform_bulk_action_ess.ts` functional test. ## Details `perform_bulk_action_ess.ts` includes a number of functional tests where some of them were flaky. Investigation revealed that creating enabled rules and performing bulk actions may lead to race conditions. Under that conditions rule's SO isn't updated as expected. For example legacy rule actions aren't persisted in rule's SO when it's expected by the test. This PR includes `perform_bulk_action_ess.ts` refactoring to create disabled rules in the majority of tests. Enabled rules are created only in tests checking behavior upon rules disabling. These tests were checked multiple times and didn't demonstrate flakiness. Additionally `@kbn/expect` was replaced with `expect` to make asserting more transparent and avoid unclear error messages. ## Flaky test results [100 runs](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7274) 🟢 (cherry picked from commit bf37a01)
…#197660) **Closes: elastic#196470 **Closes: elastic#196462 ## Summary This PR unskips `perform_bulk_action_ess.ts` functional test. ## Details `perform_bulk_action_ess.ts` includes a number of functional tests where some of them were flaky. Investigation revealed that creating enabled rules and performing bulk actions may lead to race conditions. Under that conditions rule's SO isn't updated as expected. For example legacy rule actions aren't persisted in rule's SO when it's expected by the test. This PR includes `perform_bulk_action_ess.ts` refactoring to create disabled rules in the majority of tests. Enabled rules are created only in tests checking behavior upon rules disabling. These tests were checked multiple times and didn't demonstrate flakiness. Additionally `@kbn/expect` was replaced with `expect` to make asserting more transparent and avoid unclear error messages. ## Flaky test results [100 runs](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7274) 🟢 (cherry picked from commit bf37a01)
New failure: kibana-on-merge - 8.16 |
New failure: kibana-on-merge - 8.16 |
New failure: kibana-on-merge - 8.16 |
… bulk action FTR test (#199200) **Addresses:** #196462 ## Summary `perform_bulk_action_ess.ts`'s `ESS specific logic` -> `should disable rules and migrate actions` FTR test is flaky in `8.16`. This skips only this particular test. ## More details on flakiness Flakiness isn't reproducible in `main` which is `v9.0` currently. It's suspected that modification of rule's SO interferences with rules bulk action performing a legacy action migration. Though a quick fix like waiting for rule execution completion before performing bulk action didn't help. It requires further investigation. Another idea `8.16` could require some PR from to be backported which fixed this issue in `main`.
A test failed on a tracked branch
First failure: kibana-on-merge - main
Todo
The text was updated successfully, but these errors were encountered: