[Session] Fix bug with Session index creation and update when using 8.x with a 7.x data archive. #208243
Assignees
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Security/Session Management
Platform Security - Session Management
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Comments
SiddharthMantri
added
bug
|
Pinging @elastic/kibana-security (Team:Security) |
9 tasks
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jan 29, 2025
…08244) Closes elastic#208243 ## Summary [This PR](elastic#204097) introduced an unintended issue for users running 8.x with a 7.x archive. This has been fixed by correctly searching for existing index by both name and alias. ### To test: You can follow the same steps as the above PR: elastic#204097 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 449ac98)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this PR: #204097, we switched from using the index name for searching and used the alias only. If the alias did not exist, we applied the "new mappings" and created the index. And if it did exist, we did nothing. The backport to 8.x had an unintended consequence where calling the index exists API with the alias returned false if searching against a 7.x archive.
The text was updated successfully, but these errors were encountered: