Skip to content

[CI] DockerTests test171AdditionalCliOptionsAreForwarded failing #120925

Open
@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.RuntimeException: Request failed:
HTTP/1.1 401 Unauthorized
{"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm=\"security\"","ApiKey","Basic realm=\"security\", charset=\"UTF-8\""]}}],"type":"security_exception","reason":"unable to authenticate user [elastic] for REST request [/]","header":{"WWW-Authenticate":["Bearer realm=\"security\"","ApiKey","Basic realm=\"security\", charset=\"UTF-8\""]}},"status":401}

Issue Reasons:

  • [main] 13 failures in test test171AdditionalCliOptionsAreForwarded (3.1% fail rate in 421 executions)
  • [main] 2 failures in step rhel-8_packaging-tests-unix (50.0% fail rate in 4 executions)
  • [main] 2 failures in step ubuntu-2004_destructivedistrotest.docker_packaging-tests-unix-sample (1.3% fail rate in 159 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic-packaging (75.0% fail rate in 4 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.2% fail rate in 161 executions)

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

Metadata

Metadata

Labels

:Security/SecuritySecurity issues without another label>test-failureTriaged test failures from CITeam:SecurityMeta label for security teamlow-riskAn open issue or test failure that is a low risk to future releases

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions