-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Open
Labels
:Delivery/PackagingRPM and deb packaging, tar and zip archives, shell and batch scriptsRPM and deb packaging, tar and zip archives, shell and batch scripts>test-failureTriaged test failures from CITriaged test failures from CITeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
Description
Build Scans:
- elasticsearch-periodic-packaging #9283 / debian-11_packaging-tests-unix
- elasticsearch-periodic-packaging #9234 / rhel-7_packaging-tests-unix
- elasticsearch-periodic-packaging #9220 / rhel-7_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] 3 failures in test test124CanRestartContainerWithStackLoggingConfig (0.7% fail rate in 416 executions)
- [8.17] 2 failures in step rhel-7_packaging-tests-unix (22.2% fail rate in 9 executions)
- [8.17] 3 failures in pipeline elasticsearch-periodic-packaging (30.0% fail rate in 10 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
Labels
:Delivery/PackagingRPM and deb packaging, tar and zip archives, shell and batch scriptsRPM and deb packaging, tar and zip archives, shell and batch scripts>test-failureTriaged test failures from CITriaged test failures from CITeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)