-
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] FileSettingsRoleMappingUpgradeIT testRoleMappingsAppliedOnUpgrade {upgradedNodes=3} failing #115410
Labels
needs:risk
Requires assignment of a risk label (low, medium, blocker)
: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
elasticsearchmachine
added
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
>test-failure
Triaged test failures from CI
labels
Oct 23, 2024
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
Oct 23, 2024
Duplicate of: #115411 |
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 23, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: #115410 Resolves: #115411
n1v0lg
added a commit
to n1v0lg/elasticsearch
that referenced
this issue
Oct 23, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: elastic#115410 Resolves: elastic#115411
n1v0lg
added a commit
to n1v0lg/elasticsearch
that referenced
this issue
Oct 23, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: elastic#115410 Resolves: elastic#115411
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 23, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: #115410 Resolves: #115411
smalyshev
pushed a commit
to smalyshev/elasticsearch
that referenced
this issue
Oct 23, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: elastic#115410 Resolves: elastic#115411
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 24, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: #115410 Resolves: #115411 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
georgewallace
pushed a commit
to georgewallace/elasticsearch
that referenced
this issue
Oct 25, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: elastic#115410 Resolves: elastic#115411
jfreden
pushed a commit
to jfreden/elasticsearch
that referenced
this issue
Nov 4, 2024
Fixes some faulty assertions in an upgrade test. Test failures only manifest on the 8.16 branch since 9.x does not qualify for these upgrade tests, and the change is not backported to 8.17 yet (unrelated CI failures). I validated this works by running it locally from the 8.16 branch. Resolves: elastic#115410 Resolves: elastic#115411
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
needs:risk
Requires assignment of a risk label (low, medium, blocker)
: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
Build Scans:
Reproduction Line:
Applicable branches:
8.16
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: