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 ES Promotion: FTR Configs #96 / Alerts APIs - Trial License/Complete Tier @ess Alerts Compatibility EQL should generate a signal-on-legacy-signal with AAD index pattern #176270

Closed
mistic opened this issue Feb 6, 2024 · 6 comments
Closed

Failing ES Promotion: FTR Configs #96 / Alerts APIs - Trial License/Complete Tier @ess Alerts Compatibility EQL should generate a signal-on-legacy-signal with AAD index pattern #176270

mistic opened this issue Feb 6, 2024 · 6 comments
Assignees
@yctercero @vitaliidm
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. reason:legit-failure Denotes that test failure is a legitimate bug, not a system flake. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Milestone
D&R 8.13

Comments

@mistic
Copy link
Member

mistic commented Feb 6, 2024

Detection Engine - Alerts Integration Tests - ESS Env - Trial License
x-pack/test/security_solution_api_integration/test_suites/detections_response/detection_engine/alerts/trial_license_complete_tier/alerts_compatibility.ts

Alerts APIs - Trial License/Complete Tier @ess Alerts Compatibility EQL should generate a signal-on-legacy-signal with AAD index pattern

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

For more information on the Elasticsearch snapshot process including how to reproduce using the unverified ES build please read the failed promotion annotation. Other important information can be found at:

Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/var/lib/buildkite-agent/builds/kb-n2-4-spot-7a1f7168f11c4e81/elastic/kibana-elasticsearch-snapshot-verify/kibana/x-pack/test/security_solution_api_integration/test_suites/detections_response/detection_engine/alerts/trial_license_complete_tier/alerts_compatibility.ts)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7) {
  code: 'ERR_MOCHA_TIMEOUT',
  timeout: 360000,
  file: '/var/lib/buildkite-agent/builds/kb-n2-4-spot-7a1f7168f11c4e81/elastic/kibana-elasticsearch-snapshot-verify/kibana/x-pack/test/security_solution_api_integration/test_suites/detections_response/detection_engine/alerts/trial_license_complete_tier/alerts_compatibility.ts'
}
@mistic mistic added blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test failed-es-promotion Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Engine Security Solution Detection Engine Area v8.13.0 labels Feb 6, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

mistic added a commit that referenced this issue Feb 6, 2024
@mistic
skip flaky es promotion suite (#176270)
7e805a4
@mistic
Copy link
Member Author

mistic commented Feb 6, 2024

Skipped.

main: 7e805a4

fkanout pushed a commit to fkanout/kibana that referenced this issue Feb 7, 2024
@mistic @fkanout
skip flaky es promotion suite (elastic#176270)
eb9325b
@yctercero yctercero added reason:legit-failure Denotes that test failure is a legitimate bug, not a system flake. impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed triage_needed labels Feb 7, 2024
@yctercero
Copy link
Contributor

Related to other similar legitimate failures. This failure is blocking for us.

See discussion: #176105 (comment)

@yctercero yctercero mentioned this issue Feb 12, 2024
Merged
@yctercero yctercero added this to the D&R 8.13 milestone Feb 12, 2024
yctercero added a commit that referenced this issue Feb 14, 2024
@yctercero
[Detections Response][Tests] Unskip tests (#176661)
c57da8b 
## Summary

Unskips tests that were skipped due to an upstream change and fixed in
elastic/elasticsearch#105298

Addresses #176105,
#176117,
#176270,
#176359,
#176360
@yctercero
Copy link
Contributor

Confirmed fix upstream #176661

CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
@mistic @CoenWarmer
skip flaky es promotion suite (elastic#176270)
d2de97c
CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this issue Feb 15, 2024
@yctercero @CoenWarmer
[Detections Response][Tests] Unskip tests (elastic#176661)
15c4911 
## Summary

Unskips tests that were skipped due to an upstream change and fixed in
elastic/elasticsearch#105298

Addresses elastic#176105,
elastic#176117,
elastic#176270,
elastic#176359,
elastic#176360
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
@mistic @fkanout
skip flaky es promotion suite (elastic#176270)
35dd201
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
@yctercero @fkanout
[Detections Response][Tests] Unskip tests (elastic#176661)
aba5866 
## Summary

Unskips tests that were skipped due to an upstream change and fixed in
elastic/elasticsearch#105298

Addresses elastic#176105,
elastic#176117,
elastic#176270,
elastic#176359,
elastic#176360
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yctercero yctercero

@vitaliidm vitaliidm

Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. reason:legit-failure Denotes that test failure is a legitimate bug, not a system flake. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
D&R 8.13
Development

No branches or pull requests
6 participants
@mistic @banderror @yctercero @elasticmachine @kibanamachine @vitaliidm