-
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: 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
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
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Oct 5, 2022
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Oct 5, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
mikecote
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Oct 6, 2022
github-project-automation
bot
moved this from Todo
to Done
in AppEx: ResponseOps - Execution & Connectors
Jan 5, 2023
New failure: CI Build - main |
New failure: CI Build - main |
/skip |
1 similar comment
/skip |
Skipped main: 2ed2488 |
kibanamachine
added a commit
that referenced
this issue
Mar 27, 2023
New failure: CI Build - main |
mikecote
moved this from Done
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Mar 27, 2023
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
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]>
github-project-automation
bot
moved this from In Progress
to Done
in AppEx: ResponseOps - Execution & Connectors
Mar 29, 2023
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)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: