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.

Sign up for GitHub

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

Jump to bottom

[CI] RealmsTests testDisabledRealmsAreNotAdded #70378

Closed
davidkyle opened this issue Mar 15, 2021 · 2 comments · Fixed by #70392
Closed

[CI] RealmsTests testDisabledRealmsAreNotAdded #70378

davidkyle opened this issue Mar 15, 2021 · 2 comments · Fixed by #70392
Assignees
@ywangd
Labels
:Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@davidkyle
Copy link
Member

Build scan:
https://gradle-enterprise.elastic.co/s/hkbv57gppt62i
https://gradle-enterprise.elastic.co/s/ax54xsy3dvan4

Repro line:

./gradlew ':x-pack:plugin:security:test' --tests "org.elasticsearch.xpack.security.authc.RealmsTests.testDisabledRealmsAreNotAdded" \
  -Dtests.seed=26D54A457F1571D8 \
  -Dtests.security.manager=true \
  -Dtests.locale=th \
  -Dtests.timezone=America/Halifax \
  -Druntime.java=8

Reproduces locally?:
Yes

Applicable branches:
7.x

Failure history:
2 today

Failure excerpt:

java.lang.AssertionError: unexpected warning headers
Expected: an empty collection
     but: <[299 Elasticsearch-7.13.0-SNAPSHOT-f15c31f846d0f3951c4913fba1d5cfdc313b4d7d "Found explicitly disabled basic realms: [file,native]. But they will be enabled because no other realms are configured or enabled. In next major release, explicitly disabled basic realms will remain disabled."]>
	at __randomizedtesting.SeedInfo.seed([809D7B2D3C3BEA97:86A181955AC7CE7]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
	at org.junit.Assert.assertThat(Assert.java:956)
	at org.elasticsearch.test.ESTestCase.ensureNoWarnings(ESTestCase.java:427)
@davidkyle davidkyle added >test-failure Triaged test failures from CI :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) labels Mar 15, 2021
@elasticmachine elasticmachine added the Team:Security Meta label for security team label Mar 15, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@davidkyle davidkyle mentioned this issue Mar 15, 2021
Merged
@ywangd ywangd self-assigned this Mar 15, 2021
@ywangd ywangd mentioned this issue Mar 15, 2021
Merged
@ywangd
Copy link
Member

ywangd commented Mar 15, 2021

Thanks @davidkyle I raised #70392.

@ywangd ywangd linked a pull request Mar 15, 2021 that will close this issue
[Tests] Handle warning when all realms are disabled #70392
Merged
ywangd added a commit that referenced this issue Apr 19, 2021
@ywangd
[Test] Handle warning when all realms are disabled (#70392)
3ceb34e 
When all configured realms are disabled, the new warning added by #69320 needs to be handled.

Resolves: #70378
@ywangd ywangd closed this as completed Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ywangd ywangd

Labels
:Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Tests] Handle warning when all realms are disabled ywangd/elasticsearch
3 participants
@ywangd @davidkyle @elasticmachine