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 ES Promotion: Actions and Triggers app Alert Details Alert Instances "before all" hook for "renders the active alert instances #71559

Closed
tylersmalley opened this issue Jul 13, 2020 · 4 comments · Fixed by #71632
Labels
blocker failed-es-promotion Feature:Alerting skipped-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.9.0 v8.0.0

Comments

@tylersmalley
Copy link
Contributor

This failure is preventing the promotion of the current Elasticsearch nightly snapshot.

main/8.0.0: https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/1077/execution/node/416/log/
7x/7.9: https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/1076/execution/node/421/log/

For more information on the Elasticsearch snapshot promotion process: https://www.elastic.co/guide/en/kibana/master/development-es-snapshots.html

14:00:56         │1)    Actions and Triggers app
14:00:56         │       Alert Details
14:00:56         │         Alert Instances
14:00:56         │           "before all" hook for "renders the active alert instances":
14:00:56         │
14:00:56         │      retry.try timeout: Error: expected 0 to sort of equal 3
14:00:56         │     at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
14:00:56         │     at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
14:00:56         │     at retry.try (/dev/shm/workspace/kibana/x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/details.ts:365:57)
14:00:56         │     at process._tickCallback (internal/process/next_tick.js:68:7)
14:00:56         │   Error: retry.try timeout: Error: expected 0 to sort of equal 3
14:00:56         │       at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
14:00:56         │       at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
14:00:56         │       at retry.try (test/functional_with_es_ssl/apps/triggers_actions_ui/details.ts:365:57)
14:00:56         │       at process._tickCallback (internal/process/next_tick.js:68:7)
14:00:56         │       at onFailure (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
14:00:56         │       at retryForSuccess (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:68:13)
@tylersmalley tylersmalley added blocker Feature:Alerting v8.0.0 Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.9.0 failed-es-promotion labels Jul 13, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

tylersmalley pushed a commit that referenced this issue Jul 13, 2020
#71559

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley pushed a commit that referenced this issue Jul 13, 2020
#71559

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
@tylersmalley
Copy link
Contributor Author

Skipped:

main/8.0: b217cb3
7.x/7.9: 40a2343

@tylersmalley
Copy link
Contributor Author

Possibly related to #71558 and/or #71555

@tylersmalley
Copy link
Contributor Author

Confirmed this failure, along with those linked above, were introduced in elastic/elasticsearch@a28ce1e

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-es-promotion Feature:Alerting skipped-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants