[Cloud Security] Fix flaky test

[CohenIdo]

Solves:

• Failing test: Serverless Security API Integration Tests.x-pack/test_serverless/api_integration/test_suites/security/cloud_security_posture/benchmark/v1·ts - Serverless security API cloud_security_posture GET /internal/cloud_security_posture/benchmark "before each" hook for "Should return non-empty array filled with Rules if user has CSP integrations" #182570
• Failing test: Serverless Security API Integration Tests.x-pack/test_serverless/api_integration/test_suites/security/cloud_security_posture/status/status_indexing·ts - Serverless security API cloud_security_posture GET /internal/cloud_security_posture/status STATUS = INDEXING TEST "before each" hook for "Return kspm status indexing when logs-cloud_security_posture.findings_latest-default doesn't contain new kspm documents, but has newly connected agents" #181777
• 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" #178027

---

The tests mentioned above failed with the following error message:

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...

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 previously skipped tests, I executed the tests using the flaky test runner, and it appears that this action has resolved the issue.

[elasticmachine]

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

[kfirpeled]

@CohenIdo please elaborate on the ticket's description of what stands behind this fix. This will serve us in the future as a knowledge base

[CohenIdo]

@elasticmachine merge upstream

[CohenIdo]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: ce87218

Metrics [docs]

✅ unchanged

History

• 💛 Build #210047 was flaky 3c290f7
• 💚 Build #209615 succeeded cb1577b
• 💛 Build #209475 was flaky 8071c67

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream