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.

Sign up for GitHub

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

Jump to bottom

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 superuser at space1 should schedule actions on legacy alerts #140867

Closed
kibanamachine opened this issue Sep 15, 2022 · 19 comments · Fixed by #151802 or #153803
Closed

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 superuser at space1 should schedule actions on legacy alerts #140867

kibanamachine opened this issue Sep 15, 2022 · 19 comments · Fixed by #151802 or #153803
Assignees
@mikecote
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 Sep 15, 2022 •
edited
Loading

A test failed on a tracked branch

Error: expected 409 to sort of equal 204
    at Assertion.assert (node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.eql (node_modules/@kbn/expect/expect.js:244:8)
    at Context.<anonymous> (x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/alerting/rbac_legacy.ts:117:56)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (node_modules/@kbn/test/target_node/src/functional_test_runner/lib/mocha/wrap_function.js:87:16) {
  actual: '409',
  expected: '204',
  showDiff: true
}

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

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 15, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@doakalexi doakalexi moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Execution & Connectors Oct 20, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Nov 30, 2022
@mistic
skip flaky suite (#140867)
6085bea
@mistic
Copy link
Member

mistic commented Nov 30, 2022

Skipped.

main: 6085bea

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.6

jbudz pushed a commit that referenced this issue Dec 1, 2022
@mistic @jbudz
skip flaky suite (#140867)
f2ca6d3
@jbudz
Copy link
Member

jbudz commented Dec 1, 2022

8.6: f2ca6d3

@jbudz jbudz added the v8.6.0 label Dec 1, 2022
@doakalexi doakalexi self-assigned this Feb 7, 2023
@doakalexi doakalexi moved this from Todo to In Progress in AppEx: ResponseOps - Execution & Connectors Feb 7, 2023
@doakalexi doakalexi assigned doakalexi and unassigned doakalexi Feb 13, 2023
@doakalexi doakalexi moved this from In Progress to Todo in AppEx: ResponseOps - Execution & Connectors Feb 13, 2023
@doakalexi doakalexi removed their assignment Feb 13, 2023
@mikecote mikecote moved this from Todo to In Progress in AppEx: ResponseOps - Execution & Connectors Feb 16, 2023
@mikecote mikecote self-assigned this Feb 16, 2023
@mikecote
Copy link
Contributor

I took a quick look at the test failures and saw the following message

rulesClient.updateApiKey('f785e6fd-6401-567a-bf00-204bbf1fd347') conflict, exceeded retries

Making me think this isn't related to task manager bulk enable / disable. I'll unassign myself for now.

@mikecote mikecote removed their assignment Feb 16, 2023
@kibanamachine kibanamachine reopened this Mar 27, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@jbudz
Copy link
Member

jbudz commented Mar 27, 2023

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: c012199

kibanamachine added a commit that referenced this issue Mar 27, 2023
@kibanamachine
skip failing test suite (#140867)
c012199
@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 mikecote assigned mikecote and unassigned ersin-erdal Mar 27, 2023
@mikecote mikecote moved this from Done to In Progress in AppEx: ResponseOps - Execution & Connectors Mar 27, 2023
@mikecote mikecote mentioned this issue Mar 27, 2023
Merged
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

jgowdyelastic pushed a commit to jgowdyelastic/kibana that referenced this issue Mar 30, 2023
@mikecote @kibanamachine @jgowdyelastic
Fix flaky RBAC Legacy test due to archive containing tasks and rules …
d7e682a 
…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
Assignees

@mikecote mikecote

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
AppEx: ResponseOps - Execution & Connectors
Status: Done
Milestone
No milestone
7 participants
@jbudz @mikecote @mistic @elasticmachine @kibanamachine @ersin-erdal @doakalexi