Failing test: Serverless Security API Integration Tests.x-pack/test_serverless/api_integration/test_suites/security/cloud_security_posture/status/status_indexed·ts - Serverless security API cloud_security_posture GET /internal/cloud_security_posture/status STATUS = INDEXED TEST "before each" hook for "Return kspm status indexed when logs-cloud_security_posture.findings_latest-default contains new kspm documents"

[kibanamachine]

A test failed on a tracked branch

ResponseError: {"_shards":{"total":8,"successful":7,"failed":1,"failures":[{"shard":0,"index":".ds-metrics-fleet_server.agent_status-default-2024.03.05-000001","status":"NOT_FOUND","reason":{"type":"index_not_found_exception","reason":"no such index [.ds-metrics-fleet_server.agent_status-default-2024.03.05-000001]","index_uuid":"etT2dd-cQnuehaMWQcu4bg","index":".ds-metrics-fleet_server.agent_status-default-2024.03.05-000001"}}]}}
    at SniffingTransport.request (node_modules/@elastic/transport/src/Transport.ts:535:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Indices.refresh (node_modules/@elastic/elasticsearch/src/api/api/indices.ts:1482:12)
    at loadAction (load.ts:124:3)
    at EsArchiver.load (es_archiver.ts:99:12)
    at Context.<anonymous> (status_indexed.ts:53:9)
    at Object.apply (wrap_function.js:73:16) {
  meta: {
    body: { _shards: [Object] },
    statusCode: 404,
    headers: {
      'x-elastic-product': 'Elasticsearch',
      'elastic-api-version': '2023-10-31',
      'content-type': 'application/json',
      'content-length': '418'
    },
    meta: {
      context: null,
      request: [Object],
      name: 'elasticsearch-js',
      connection: [Object],
      attempts: 0,
      aborted: false
    },
    warnings: [Getter]
  }
}

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[mistic]

Skipped.

main: b0b73ad

[kfirpeled]

@animehart fyi, @CohenIdo is working on a similar issue in our tests #182570

Ido, please update and unskip the tests incase you figure out a solution for #182570

[CohenIdo]

While addressing the issue documented in #182570, I identified that the test failure in this issue occurred due to a similar error ( failure in writing to the data stream named .ds-metrics-fleet_server).

I consulted with the fleet team and discovered that there is a task responsible for writing to the data stream named ds-metrics-fleet_server, and it was recommended to disable this task during FTRs.

After updating the test configuration to disable this task and re-enabling the skipped test, I executed the tests using the flaky test runner, and it appears that this action has resolved the issue.