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: FTR Configs #41 / machine learning - anomaly detection aggregated or scripted job supported job with aggregation field "before all" hook for "opens a job from job list link" #178562

Closed
mistic opened this issue Mar 12, 2024 · 5 comments
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test :ml

Comments

@mistic
Copy link
Member

mistic commented Mar 12, 2024

Chrome X-Pack UI Functional Tests - ML anomaly_detection_result_views
x-pack/test/functional/apps/ml/anomaly_detection_result_views/aggregated_scripted_job.ts

machine learning - anomaly detection aggregated or scripted job supported job with aggregation field "before all" hook for "opens a job from job list link"

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: Expected status code 200, got 400 with body '{"statusCode":400,"error":"Bad Request","message":"[x_content_parse_exception\n\tRoot causes:\n\t\tx_content_parse_exception: [1:45] [job_details] unknown field [job_type]]: [1:45] [job_details] unknown field [job_type]","attributes":{"body":{"error":{"root_cause":[{"type":"x_content_parse_exception","reason":"[1:45] [job_details] unknown field [job_type]"}],"type":"x_content_parse_exception","reason":"[1:45] [job_details] unknown field [job_type]"},"status":400}}}'
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Object.assertResponseStatusCode (api.ts:87:31)
    at Object.createAnomalyDetectionJob (api.ts:692:12)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.createAndRunAnomalyDetectionLookbackJob (api.ts:872:7)
    at Context.<anonymous> (aggregated_scripted_job.ts:381:11)
    at Object.apply (wrap_function.js:73:16) {
  actual: '400',
  expected: '200',
  showDiff: true
}
@mistic mistic added blocker :ml failed-test A test failure on a tracked branch, potentially flaky-test skipped-test failed-es-promotion v8.14.0 labels Mar 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@mistic
Copy link
Member Author

mistic commented Mar 12, 2024

Skipped.

main: b285c3a

@droberts195
Copy link
Contributor

@jan-elastic I think the create job API will have to accept job_type after all. But the only permitted value should be anomaly_detector.

@jan-elastic
Copy link

jan-elastic commented Mar 13, 2024

Reverting the commit for now: elastic/elasticsearch#106277, so we can discuss how to proceed.

jgowdyelastic added a commit that referenced this issue Mar 18, 2024
`job_type` should not be part of the job config when creating a job.
This was accidentally left in for some test data.

Related to #178562 and
elastic/elasticsearch#106277
saikatsarkar056 pushed a commit to saikatsarkar056/kibana that referenced this issue Mar 21, 2024
`job_type` should not be part of the job config when creating a job.
This was accidentally left in for some test data.

Related to elastic#178562 and
elastic/elasticsearch#106277
@qn895
Copy link
Member

qn895 commented Mar 28, 2024

Closing via #178715

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-es-promotion failed-test A test failure on a tracked branch, potentially flaky-test :ml
Projects
None yet
Development

No branches or pull requests

6 participants