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: Entity Analytics - Risk Engine Integration Tests - Serverless Env - Complete Tier.x-pack/test/security_solution_api_integration/test_suites/entity_analytics/risk_engine/trial_license_complete_tier/init_and_status_apis·ts - Entity Analytics - Risk Engine @ess @serverless @serverlessQA init_and_status_apis init api should remove legacy risk score transform if it exists #191637

Open
kibanamachine opened this issue Aug 28, 2024 · 13 comments
Labels
blocker failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Entity Analytics Security Entity Analytics Team v8.16.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Aug 28, 2024

A test failed on a tracked branch

ResponseError: resource_not_found_exception
	Root causes:
		resource_not_found_exception: Transform with id [ml_hostriskscore_pivot_transform_default] could not be found
    at SniffingTransport._request (node_modules/@elastic/transport/src/Transport.ts:601:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at /opt/buildkite-agent/builds/bk-agent-prod-gcp-1724851580616668417/elastic/kibana-elasticsearch-serverless-verify-and-promote/kibana/node_modules/@elastic/transport/src/Transport.ts:704:22
    at SniffingTransport.request (node_modules/@elastic/transport/src/Transport.ts:701:14)
    at Transform.getTransform (node_modules/@elastic/elasticsearch/src/api/api/transform.ts:145:12)
    at Context.<anonymous> (init_and_status_apis.ts:306:22)
    at Object.apply (wrap_function.js:73:16) {
  options: { redaction: { type: 'replace', additionalKeys: [] } },
  meta: {
    body: { error: [Object], status: 404 },
    statusCode: 404,
    headers: {
      'x-elastic-product': 'Elasticsearch',
      'elastic-api-version': '2023-10-31',
      'content-type': 'application/json',
      'content-length': '299'
    },
    meta: {
      context: null,
      request: [Object],
      name: 'elasticsearch-js',
      connection: [Object],
      attempts: 0,
      aborted: false
    },
    warnings: null
  }
}

First failure: kibana-elasticsearch-serverless-verify-and-promote - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Aug 28, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 28, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Aug 28, 2024
@kibanamachine
Copy link
Contributor Author

@jaredburgettelastic
Copy link
Contributor

Will have a team member look at this test. However, for external communication purposes, this test specific failing should not be a blocker on Serverless promotion, because the legacy risk scoring transform (which this test refers to) was never accessible to customers on Serverless.

@mistic
Copy link
Member

mistic commented Aug 29, 2024

@jaredburgettelastic does it means we can actually skip this test until your team figures it out to avoid having it failing in some serverless promotion pipeline?

@jaredburgettelastic
Copy link
Contributor

@mistic yes, please feel free to skip for now if this is preventing promotion

@kibanamachine
Copy link
Contributor Author

@kibanamachine
Copy link
Contributor Author

@delanni
Copy link
Contributor

delanni commented Aug 29, 2024

With the above in mind, I'm skipping this.

@delanni
Copy link
Contributor

delanni commented Aug 29, 2024

/skip

@kibanamachine
Copy link
Contributor Author

Skipped

main: 7adda78

@rayafratkina
Copy link
Contributor

@jaredburgettelastic is the team working on a fix for the underlying issue and do we expect a solution soon?

@jaredburgettelastic
Copy link
Contributor

Hey @rayafratkina !

Per the conversation above, I mentioned that this was less of a priority from our side due to this legacy feature not being relevant for serverless.

Since it sounds like this is more of a priority for platform due to how the issue is being tracked, I'll have someone take a look at it tomorrow. Thank you!

@jaredburgettelastic jaredburgettelastic self-assigned this Oct 1, 2024
@jaredburgettelastic
Copy link
Contributor

jaredburgettelastic commented Oct 9, 2024

First stop-gap: #195651

@jaredburgettelastic jaredburgettelastic removed their assignment Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Entity Analytics Security Entity Analytics Team v8.16.0
Projects
None yet
Development

No branches or pull requests

6 participants