-
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
Simulate index fails when index name already exists and has an alias #84256
Labels
Comments
arteam
added
the
:Data Management/Indices APIs
APIs to create and manage indices and templates
label
Feb 23, 2022
elasticmachine
added
the
Team:Data Management
Meta label for data/management team
label
Feb 23, 2022
Pinging @elastic/es-data-management (Team:Data Management) |
arteam
removed
Team:Data Management
Meta label for data/management team
needs:triage
Requires assignment of a team area label
labels
Feb 23, 2022
This bug is causing multiple automated tests in Security Solution to fail in CI builds. Furthermore, it breaks existing functionality around our "alerts on alerts" feature of Detection Rules. It's also causing the issue reported in this ticket. Help prioritizing a fix would be greatly appreciated. 🙏 |
@peluja1012 yep, I'll take a look at this. |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Mar 4, 2022
…emplate Previously when constructing the "fake" response when simulating an index template (`/_index_template/_simulate_index/<myindexname>`) an error would be thrown if there was an index, alias, or data stream already existing with the provided index name. This commit makes it so that simulating an index that may already exist treats it as though it was a new creation of the index. Resolves elastic#84256
This was referenced Mar 14, 2022
FrankHassanabad
added a commit
to elastic/kibana
that referenced
this issue
Mar 15, 2022
…126294) ## Summary Increases the timeouts from 2 minutes to now 5 minutes and unskips the detection tests. If any of the tests fail consistently then I will skip just those individual tests instead of the whole suit. See #125851 and elastic/elasticsearch#84256 This could cause issues with: #125319 If so, then we will have to deal with the cloud based tests in a different way but in reality we need the extra time as some test cases do take a while to run on CI. This also: * Removes skips around code that have been in there for a while and adds documentation to the parts that are left over. ### Checklist - [x] [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
maksimkovalev
pushed a commit
to maksimkovalev/kibana
that referenced
this issue
Mar 18, 2022
…lastic#126294) ## Summary Increases the timeouts from 2 minutes to now 5 minutes and unskips the detection tests. If any of the tests fail consistently then I will skip just those individual tests instead of the whole suit. See elastic#125851 and elastic/elasticsearch#84256 This could cause issues with: elastic#125319 If so, then we will have to deal with the cloud based tests in a different way but in reality we need the extra time as some test cases do take a while to run on CI. This also: * Removes skips around code that have been in there for a while and adds documentation to the parts that are left over. ### Checklist - [x] [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
jsoriano
added a commit
to elastic/elastic-package
that referenced
this issue
Jul 4, 2024
Use a different data stream name when simulating to check if synthetic is enabled. There seems to be some conflict if the same name is reused. Maybe related to elastic/elasticsearch#84256 or some similar issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Elasticsearch Version
8.2.0
Installed Plugins
No response
Java Version
bundled
OS Version
Darwin Kernel Version 20.6.0
Problem Description
The simulate index API returns an error if used with an index name that already exists and the existing index has an alias defined.
Previously in 8.0 the simulate index API would return the expected mappings, settings, and aliases even when used with an index name that already exists.
Steps to Reproduce
Logs (if relevant)
The text was updated successfully, but these errors were encountered: