-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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] DocsClientYamlTestSuiteIT test {yaml=reference/rest-api/security/invalidate-tokens/line_194} failing #121337
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
This has been muted on branch main Mute Reasons:
Build Scans: |
elasticsearchmachine
added a commit
that referenced
this issue
Jan 30, 2025
…=reference/rest-api/security/invalidate-tokens/line_194} #121337
Pinging @elastic/es-delivery (Team:Delivery) |
smalyshev
pushed a commit
to smalyshev/elasticsearch
that referenced
this issue
Jan 30, 2025
…=reference/rest-api/security/invalidate-tokens/line_194} elastic#121337
saikatsarkar056
pushed a commit
to saikatsarkar056/elasticsearch
that referenced
this issue
Jan 31, 2025
…=reference/rest-api/security/invalidate-tokens/line_194} elastic#121337
Pinging @elastic/es-security (Team:Security) |
jfreden
pushed a commit
to jfreden/elasticsearch
that referenced
this issue
Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103
slobodanadamovic
added a commit
to slobodanadamovic/elasticsearch
that referenced
this issue
Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
slobodanadamovic
added a commit
to slobodanadamovic/elasticsearch
that referenced
this issue
Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
slobodanadamovic
added a commit
to slobodanadamovic/elasticsearch
that referenced
this issue
Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves elastic#122343 Resolves elastic#121748 Resolves elastic#121611 Resolves elastic#121345 Resolves elastic#121338 Resolves elastic#121337 Resolves elastic#121288 Resolves elastic#121287 Resolves elastic#121867 Resolves elastic#122335 Resolves elastic#122681 Resolves elastic#121976 Resolves elastic#123094 Resolves elastic#123192 Resolves elastic#122983 Resolves elastic#124671 Resolves elastic#124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 13, 2025
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 13, 2025
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 13, 2025
) The .security index is created asynchronously on a cluster startup. This affects some of the docs YAML tests in a way that they need to account for the existence of the .security index or wait for the index to be created and green. This PR disables the feature for docs YAML tests. Disabling the feature in docs YAML tests will solve the flakiness without affecting the coverage. Resolves #122343 Resolves #121748 Resolves #121611 Resolves #121345 Resolves #121338 Resolves #121337 Resolves #121288 Resolves #121287 Resolves #121867 Resolves #122335 Resolves #122681 Resolves #121976 Resolves #123094 Resolves #123192 Resolves #122983 Resolves #124671 Resolves #124103 (cherry picked from commit cac356a) # Conflicts: # muted-tests.yml
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:
main
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: