[CI] DockerTests test011SecurityEnabledStatus failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-packaging #4501 / ubuntu-2204_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / ubuntu-2204_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / rocky-8_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / rocky-8_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / ubuntu-2004_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / ubuntu-2004_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / rhel-8_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / rhel-8_packaging-tests-unix

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failed to check whether Elasticsearch had started. This could be because authentication isn't working properly. Check the container logs

Issue Reasons:

• [main] 37 failures in test test011SecurityEnabledStatus (9.3% fail rate in 400 executions)
• [main] 7 failures in step ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample (8.8% fail rate in 80 executions)
• [main] 6 failures in step rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample (7.5% fail rate in 80 executions)
• [main] 7 failures in pipeline elasticsearch-pull-request (8.6% fail rate in 81 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

This has been muted on branch main

Mute Reasons:

• [main] 15 failures in test test011SecurityEnabledStatus (4.3% fail rate in 345 executions)
• [main] 7 failures in step ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample (8.8% fail rate in 80 executions)
• [main] 6 failures in step rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample (7.5% fail rate in 80 executions)
• [main] 7 failures in pipeline elasticsearch-pull-request (8.6% fail rate in 81 executions)

Build Scans:

• elasticsearch-periodic-packaging #4501 / ubuntu-1804_packaging-tests-unix
• elasticsearch-periodic-packaging #4501 / ubuntu-1804_packaging-tests-unix
• elasticsearch-pull-request #40830 / ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40766 / ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40765 / rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40766 / rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40765 / ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40752 / rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40752 / ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample
• elasticsearch-pull-request #40743 / rhel-8_destructivedistrotest.docker_packaging-tests-unix-sample

[elasticsearchmachine]

Pinging @elastic/es-delivery (Team:Delivery)

[breskeby]

caused by change in ml-cpp that has been reverted for now