-
Notifications
You must be signed in to change notification settings - Fork 25k
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] FullClusterRestartIT testTransformLegacyTemplateCleanup {cluster=UPGRADED} failing #119395
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
:Delivery/Build
Build or test infrastructure
>test-failure
Triaged test failures from CI
Team:Delivery
Meta label for Delivery team
needs:risk
Requires assignment of a risk label (low, medium, blocker)
labels
Dec 31, 2024
Pinging @elastic/es-delivery (Team:Delivery) |
Same as #119259 |
mark-vieira
added
:Data Management/Watcher
and removed
:Delivery/Build
Build or test infrastructure
labels
Jan 2, 2025
elasticsearchmachine
added
Team:Data Management
Meta label for data/management team
and removed
Team:Delivery
Meta label for Delivery team
labels
Jan 2, 2025
Pinging @elastic/es-data-management (Team:Data Management) |
lukewhiting
added
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
and removed
:Data Management/Watcher
labels
Jan 7, 2025
elasticsearchmachine
added
Team:Security
Meta label for security team
and removed
Team:Data Management
Meta label for data/management team
labels
Jan 7, 2025
Pinging @elastic/es-security (Team:Security) |
This has been muted on branch 8.x Mute Reasons:
Build Scans: |
elasticsearchmachine
added a commit
that referenced
this issue
Jan 8, 2025
…rmLegacyTemplateCleanup {cluster=UPGRADED} #119395
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 10, 2025
This PR addresses an issue where legacy API keys fail consistency checks because they include synthetic role names. We removed synthetic role names with #56005. We added consistency checks sometime later to enforce no role names, with #93894 in `8.8.0`. Rather than relaxing our consistency checks, this PR tweaks de-serialization logic to strip out role names when appropriate. This has the advantage that we maintain the invariant the consistency check is meant to enforce. Note that this does not manifest in production: outside of RCS 2.0, we only execute consistency checks with assertions enabled. For RCS 2.0, an API key would require `remote_indices` privileges to ever be sent cross cluster and go through consistency checks. These were introduced after we've stopped including role names in API keys so it's not a real issue either. Closes: #119259 Closes: #119435 Closes: #119434 Closes: #119433 Closes: #119424 Closes: #119423 Closes: #119422 Closes: #119396 Closes: #119395 Closes: #119394 Closes: #119393
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.x
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: