-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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] Timeout waiting for green cluster in LicensingTests.testEnableDisableBehaviour #42215
Labels
:Security/License
License functionality for commercial features
>test-failure
Triaged test failures from CI
Comments
droberts195
added
>test-failure
Triaged test failures from CI
:Security/License
License functionality for commercial features
labels
May 20, 2019
Pinging @elastic/es-security |
Another failure today, muted this in 6.7, 6.8, 7.1, 7.2, 7.x, master |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jun 21, 2019
All valid licenses permit security, and the only license state where we don't support security is when there is a missing license. However, for safety we should attach the system (or xpack/security) user to internally originated actions even if the license is missing (or, more strictly, doesn't support security). This allows all nodes to communicate and send internal actions (shard state, handshake/pings, etc) even if a license is transitioning between a broken state and a valid state. Relates: elastic#42215
tvernum
added a commit
that referenced
this issue
Jul 3, 2019
All valid licenses permit security, and the only license state where we don't support security is when there is a missing license. However, for safety we should attach the system (or xpack/security) user to internally originated actions even if the license is missing (or, more strictly, doesn't support security). This allows all nodes to communicate and send internal actions (shard state, handshake/pings, etc) even if a license is transitioning between a broken state and a valid state. Relates: #42215
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jul 3, 2019
All valid licenses permit security, and the only license state where we don't support security is when there is a missing license. However, for safety we should attach the system (or xpack/security) user to internally originated actions even if the license is missing (or, more strictly, doesn't support security). This allows all nodes to communicate and send internal actions (shard state, handshake/pings, etc) even if a license is transitioning between a broken state and a valid state. Relates: elastic#42215 Backport of: elastic#43468
tvernum
added a commit
that referenced
this issue
Jul 3, 2019
All valid licenses permit security, and the only license state where we don't support security is when there is a missing license. However, for safety we should attach the system (or xpack/security) user to internally originated actions even if the license is missing (or, more strictly, doesn't support security). This allows all nodes to communicate and send internal actions (shard state, handshake/pings, etc) even if a license is transitioning between a broken state and a valid state. Relates: #42215 Backport of: #43468
This has been resolved by #43468, the test has been unmuted for 4 days now and hasn't failed since, so I'm closing this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Security/License
License functionality for commercial features
>test-failure
Triaged test failures from CI
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=java12,nodes=immutable&&linux&&docker/430/console failed with this error:
This does not reproduce locally using:
Looking through the test output in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=java12,nodes=immutable&&linux&&docker/430/testReport/junit/org.elasticsearch.license/LicensingTests/testEnableDisableBehaviour/ the most interesting exception might be this one:
The text was updated successfully, but these errors were encountered: