Build Scans:

• elasticsearch-periodic-packaging #9059 / debian-12_packaging-tests-unix
• elasticsearch-periodic-packaging #9052 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #9052 / rhel-9_packaging-tests-unix
• elasticsearch-periodic-packaging #9031 / rocky-9_packaging-tests-unix
• elasticsearch-periodic-packaging #9031 / opensuse-leap-15_packaging-tests-unix
• elasticsearch-periodic-packaging #9023 / opensuse-leap-15_packaging-tests-unix
• elasticsearch-periodic-packaging #9002 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #8988 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #8953 / oraclelinux-8_packaging-tests-unix
• elasticsearch-periodic-packaging #8946 / ubuntu-2204_packaging-tests-unix

Reproduction Line:

null 

Applicable branches:
8.17

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:

• [8.17] 13 failures in test test023InstallPluginUsingConfigFile (1.6% fail rate in 824 executions)
• [8.17] 4 failures in step oraclelinux-8_packaging-tests-unix (22.2% fail rate in 18 executions)
• [8.17] 2 failures in step opensuse-leap-15_packaging-tests-unix (11.8% fail rate in 17 executions)
• [8.17] 2 failures in step rhel-9_packaging-tests-unix (11.8% fail rate in 17 executions)
• [8.17] 9 failures in pipeline elasticsearch-periodic-packaging (50.0% fail rate in 18 executions)

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