Skip to content

[CI] MonitoringTribeTests failed due to setting SetOnce twice #42216

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

Closed
droberts195 opened this issue May 20, 2019 · 6 comments
Closed

[CI] MonitoringTribeTests failed due to setting SetOnce twice #42216

droberts195 opened this issue May 20, 2019 · 6 comments
Assignees
Labels
:Data Management/Monitoring :Security/TLS SSL/TLS, Certificates Team:Data Management Meta label for data/management team Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@droberts195
Copy link
Contributor

MonitoringTribeTests failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+multijob-unix-compatibility/os=redhat-8/200/console

The underlying error was:

Caused by: org.apache.lucene.util.SetOnce$AlreadySetException: The object cannot be set twice!
	at org.apache.lucene.util.SetOnce.set(SetOnce.java:69)
	at org.elasticsearch.xpack.core.XPackPlugin.setSslService(XPackPlugin.java:158)
	at org.elasticsearch.xpack.core.XPackPlugin.<init>(XPackPlugin.java:144)
	... 49 more

This did not reproduce locally using:

./gradlew :x-pack:qa:tribe-tests-with-license:unitTest \
  -Dtests.seed=6A86CE6E79045B0C \
  -Dtests.class=org.elasticsearch.xpack.monitoring.MonitoringTribeTests \
  -Dtests.security.manager=true \
  -Dtests.locale=en-US \
  -Dtests.timezone=UTC \
  -Dcompiler.java=12 \
  -Druntime.java=8

Since it's a double setting of a SetOnce I also tried to reproduce by running the whole suite:

./gradlew :x-pack:qa:tribe-tests-with-license:unitTest \
  -Dtests.seed=6A86CE6E79045B0C

That didn't reproduce either.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@tvernum tvernum added the :Security/TLS SSL/TLS, Certificates label May 20, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@tvernum tvernum self-assigned this May 20, 2019
@tvernum
Copy link
Contributor

tvernum commented May 20, 2019

Relates: #42004

tvernum added a commit to tvernum/elasticsearch that referenced this issue May 24, 2019
This test is failing on RHEL8, additional logging will help track down
the cause.

Relates: elastic#42216, elastic#42210
tvernum added a commit that referenced this issue May 24, 2019
This test is failing on RHEL8, additional logging will help track down
the cause.

Relates: #42216, #42210
@matriv
Copy link
Contributor

matriv commented May 24, 2019

@tvernum
Copy link
Contributor

tvernum commented Jun 25, 2019

This issue is on hold because our RHEL8 builds were breaking unexpectedly, so they're not currently included in the unix matrix builds.

@rjernst rjernst added Team:Data Management Meta label for data/management team Team:Security Meta label for security team labels May 4, 2020
@dakrone
Copy link
Member

dakrone commented Mar 3, 2021

Tribes is no longer a thing, so I am going to close this since it's almost two years old.

@dakrone dakrone closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Monitoring :Security/TLS SSL/TLS, Certificates Team:Data Management Meta label for data/management team Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

6 participants