Skip to content
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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy·ts - alerting api integration security and spaces enabled - Group 2 Alerts legacy alerts alerts space_1_all at space1 should schedule actions on legacy alerts #142704

Closed
kibanamachine opened this issue Oct 5, 2022 · 13 comments · Fixed by #153803
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 5, 2022

A test failed on a tracked branch

Error: retry.try timeout: Error: expected 0 to be above 0
    at Assertion.assert (node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.greaterThan.Assertion.above (node_modules/@kbn/expect/expect.js:317:8)
    at Function.greaterThan (node_modules/@kbn/expect/expect.js:531:15)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-ee0df08ed2078c43/elastic/kibana-on-merge/kibana/x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:195:83
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runAttempt (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:33:15)
    at retryForSuccess (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:71:21)
    at RetryService.try (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry.js:42:12)
    at ensureAlertIsRunning (x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:191:13)
    at Context.<anonymous> (x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:100:15)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-ee0df08ed2078c43/elastic/kibana-on-merge/kibana/node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:22:9
    at retryForSuccess (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry_for_success.js:61:13)
    at RetryService.try (node_modules/@kbn/ftr-common-functional-services/target_node/services/retry/retry.js:42:12)
    at ensureAlertIsRunning (x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:191:13)
    at Context.<anonymous> (x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:100:15)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 5, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 5, 2022
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Oct 5, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mikecote
Copy link
Contributor

/skip

1 similar comment
@jbudz
Copy link
Member

jbudz commented Mar 27, 2023

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 2ed2488

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mikecote mikecote moved this from Done to In Progress in AppEx: ResponseOps - Execution & Connectors Mar 27, 2023
@mikecote mikecote self-assigned this Mar 27, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mikecote added a commit that referenced this issue Mar 29, 2023
…together (#153803)

Resolves #153800
Resolves #142704
Resolves #153801
Resolves #142947
Resolves #140867

Similar to
#152841 (comment),
the rule and tasks archives don't seem to play nicely when combined. The
flakiness goes away when loading the rules then the tasks in sequence.
Otherwise, the tasks sometimes run before it can find the rule, causing
the task to delete itself.

I took a look at why the task would run an not be able to find the rule.
My best guess after looking at a failing flaky test is that the task
manager migration completes before the .kibana. And while .kibana
migrates, the task runs and fails to load the task because the .kibana
index is in an interim state.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2045

---------

Co-authored-by: Kibana Machine <[email protected]>
jgowdyelastic pushed a commit to jgowdyelastic/kibana that referenced this issue Mar 30, 2023
…together (elastic#153803)

Resolves elastic#153800
Resolves elastic#142704
Resolves elastic#153801
Resolves elastic#142947
Resolves elastic#140867

Similar to
elastic#152841 (comment),
the rule and tasks archives don't seem to play nicely when combined. The
flakiness goes away when loading the rules then the tasks in sequence.
Otherwise, the tasks sometimes run before it can find the rule, causing
the task to delete itself.

I took a look at why the task would run an not be able to find the rule.
My best guess after looking at a failing flaky test is that the task
manager migration completes before the .kibana. And while .kibana
migrates, the task runs and fails to load the task because the .kibana
index is in an interim state.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2045

---------

Co-authored-by: Kibana Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

5 participants