-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] LicenseDLSFLSRoleIT testQueryDLSFLSRolesShowAsDisabled failing #110729
Labels
low-risk
An open issue or test failure that is a low risk to future releases
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Comments
elasticsearchmachine
added
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
labels
Jul 10, 2024
This has been muted on branch main Mute Reasons:
Build Scans:
|
elasticsearchmachine
added a commit
that referenced
this issue
Jul 10, 2024
…SFLSRolesShowAsDisabled #110729
Pinging @elastic/es-security (Team:Security) |
elasticsearchmachine
added
Team:Security
Meta label for security team
needs:risk
Requires assignment of a risk label (low, medium, blocker)
labels
Jul 10, 2024
jfreden
added
low-risk
An open issue or test failure that is a low risk to future releases
and removed
needs:risk
Requires assignment of a risk label (low, medium, blocker)
labels
Jul 11, 2024
Looks like a test infrastructure issue. Sometimes the |
elasticsearchmachine
pushed a commit
that referenced
this issue
Aug 20, 2024
Relates: #110729 The `testQueryDLSFLSRolesShowAsDisabled` failed intermittently and my theory is that it's because applying the license of the cluster to cluster state has `NORMAL` priority and therefore sometimes (very rarely) takes more than 10 seconds. There are some related discussions to this, see: #67182, #64578 Since we're not testing the actual license lifecycle in this test, but instead how an applied license impacts the query roles API, I changed the approach to use the synchronous `/_license/start_trial` API in a `@before` so we can be sure the license was applied before we start testing. An alternative to this fix could be to increase the timeout.
Fixed in: #112002 |
lkts
pushed a commit
to lkts/elasticsearch
that referenced
this issue
Aug 20, 2024
Relates: elastic#110729 The `testQueryDLSFLSRolesShowAsDisabled` failed intermittently and my theory is that it's because applying the license of the cluster to cluster state has `NORMAL` priority and therefore sometimes (very rarely) takes more than 10 seconds. There are some related discussions to this, see: elastic#67182, elastic#64578 Since we're not testing the actual license lifecycle in this test, but instead how an applied license impacts the query roles API, I changed the approach to use the synchronous `/_license/start_trial` API in a `@before` so we can be sure the license was applied before we start testing. An alternative to this fix could be to increase the timeout.
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Sep 4, 2024
Relates: elastic#110729 The `testQueryDLSFLSRolesShowAsDisabled` failed intermittently and my theory is that it's because applying the license of the cluster to cluster state has `NORMAL` priority and therefore sometimes (very rarely) takes more than 10 seconds. There are some related discussions to this, see: elastic#67182, elastic#64578 Since we're not testing the actual license lifecycle in this test, but instead how an applied license impacts the query roles API, I changed the approach to use the synchronous `/_license/start_trial` API in a `@before` so we can be sure the license was applied before we start testing. An alternative to this fix could be to increase the timeout.
davidkyle
pushed a commit
to davidkyle/elasticsearch
that referenced
this issue
Sep 5, 2024
Relates: elastic#110729 The `testQueryDLSFLSRolesShowAsDisabled` failed intermittently and my theory is that it's because applying the license of the cluster to cluster state has `NORMAL` priority and therefore sometimes (very rarely) takes more than 10 seconds. There are some related discussions to this, see: elastic#67182, elastic#64578 Since we're not testing the actual license lifecycle in this test, but instead how an applied license impacts the query roles API, I changed the approach to use the synchronous `/_license/start_trial` API in a `@before` so we can be sure the license was applied before we start testing. An alternative to this fix could be to increase the timeout.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
low-risk
An open issue or test failure that is a low risk to future releases
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Build Scans:
Reproduction Line:
Applicable branches:
8.15
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: