Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] CertGenCliTests test40RunWithCert failing #117955

Open
elasticsearchmachine opened this issue Dec 4, 2024 · 2 comments
Open

[CI] CertGenCliTests test40RunWithCert failing #117955

elasticsearchmachine opened this issue Dec 4, 2024 · 2 comments
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Dec 4, 2024

Build Scans:

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Startup command should succeed. Stderr: [exitCode = [1] stdout = [] stderr = [Job for elasticsearch.service failed because the control process exited with error code.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.]]
Expected: <0>
     but: was <1>

Issue Reasons:

  • [main] 2 consecutive failures in step rhel-7_packaging-tests-unix
  • [main] 2 consecutive failures in step ubuntu-1804_packaging-tests-unix
  • [main] 2 consecutive failures in step oraclelinux-7_packaging-tests-unix
  • [main] 2 consecutive failures in step sles-12_packaging-tests-unix
  • [main] 12 failures in test test40RunWithCert (1.6% fail rate in 737 executions)
  • [main] 2 failures in step rhel-7_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step ubuntu-1804_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step oraclelinux-7_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step sles-12_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-packaging (50.0% fail rate in 4 executions)

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

@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Dec 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step rhel-7_packaging-tests-unix
  • [main] 2 consecutive failures in step ubuntu-1804_packaging-tests-unix
  • [main] 2 consecutive failures in step oraclelinux-7_packaging-tests-unix
  • [main] 2 consecutive failures in step sles-12_packaging-tests-unix
  • [main] 12 failures in test test40RunWithCert (1.6% fail rate in 737 executions)
  • [main] 2 failures in step rhel-7_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step ubuntu-1804_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step oraclelinux-7_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in step sles-12_packaging-tests-unix (100.0% fail rate in 2 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-packaging (50.0% fail rate in 4 executions)

Build Scans:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

1 participant